Age | Commit message (Collapse) | Author |
|
|
|
|
|
At the moment only "poweroff" and "reboot" actions are supported.
Suspend/resume requires additional changes.
|
|
After configuring a watch for the node, XenStore will asynchronously
notify the system when the value of the specified node changes with
an event message.
|
|
Turns out that we want to let devices choose whether they're issuing
XenStore requests to the backend or frontend. This also unifies the
the API somewhat as providing the xen softcore structure is now
mandatory.
|
|
into hid_desc_buf
tested by jsg
|
|
|
|
Remove leftover code that was used to set v2 of Grant Table entries.
From Nathanael Rensen <nathanael at list ! polymorpheus ! com>, thanks!
|
|
|
|
Instead of pre-allocating maximum number of Grant Table frames allotted by
the hypervisor we switch over to allocating them dynamically when the need
arises. At the same time we no longer link metadata entries representing
individual Grant Table frames as a list and use a table instead to speed
up reference lookups when establishing and removing mappings.
|
|
|
|
|
|
in the underlying information store of the host from the OpenBSD-VM's
userspace. OpenBSD did not provide access to these stores before,
mostly because we did not want to add a custom tool and interface for
each hypervisor. The pvbus(4) interface provides backends for
xen(4)'s XenStore and vmt(4)'s VMware Tools "guestinfo". These
information stores are fairly different, XenStore is a "filesystem"
while vmt is a RPC, and the key-value abstraction limits them a bit
but provides the most wanted functionality.
Discussed with many
OK mikeb@
|
|
|
|
Xen doesn't provide transmit fragment chains so initially they were
emulated but amount of grant table entries wasted in the process was
astronomical (9 times more than after this change). So while code
readability was sacrificed a bit, the change comes with a very nice
transmit performance improvement and taxes grant table references
much less than before.
|
|
Setting rxr_ and/or txr_cons_event value allows domU to delay completion
notification for receive and/or transmit ring to specified values of
consumer index. rxr_ and txr_prod_event values are updated by dom0 and
don't seem to hold any significance for us.
|
|
Grant table API is constructed in a way that once allocated grant table
entries are marked as used and cannot be given away again to some other
user. At the same time xen_grant_table_enter and _remove do not operate
on the same grant reference at the same time, so there's no need for a
lock here. Guard flag operations with memory fences to ensure correct
store/load order. This provides some decent performance improvement as
well.
|
|
This debugging check has been helpful in identifying and fixing
a few issues already. Subject to removal in the future however.
|
|
|
|
When executed under the hypervisor we need to make sure that CAS
and other atomic operations are executed while locking the bus.
Problem reported by Imre Oolberg <imre at auul ! pri ! ee>, thanks!
|
|
the generation bit to pass the tx descriptor and mbuf to the "hardware".
This way bpf is not called if vmxnet3_load_mbuf dropped the mbuf.
Tested by me
OK mikeb@
|
|
from richard proctor on bugs@
|
|
diff from richard proctor on bugs@
|
|
|
|
drivers update hardware configuration accordingly.
tested by myself, tb@, deraadt@, abieber@
ok mpi@
|
|
Figured out the hard way by Jonathon Sisson <openbsd at j3z ! org>,
thanks!
|
|
the hardware. This could have resulted in a page fault when the mbuf
has already been freed by the TX interrupt handler on another CPU.
This has the slight drawback that bpf can be called before the packet
is eventually dropped by vmxnet3_load_mbuf() - but I'm getting this
simple and verified fix in before doing further optimizations on the
start handler.
As discussed with mikeb@ jsg@ dlg@
|
|
|
|
the size of the pointer to a struct.
ok mikeb@
|
|
This avoids reading uninitialised memory when expected value types are
not present, as is currently the case with gpio signalled interrupts,
and could also be the case with buggy aml.
Without this change under certain conditions on the ideapad 100s
(such as a ramdisk kernel or generic kernel compiled with -O0)
ihidev would incorrectly attach to a bogus ioapic interrupt.
ok kettenis@
|
|
Instead of just setting bits that we think we need, do a better job of
figuring out what's supported by the backend and what's not and what do
we really need. The following improvements were implemented:
o fallback for when scatter gather I/O is not supported by Dom0;
o tcp/udp checksum offloading;
o larger mtu up to 9000: an experimental feature;
o stop requesting multicast control feature that we don't support.
|
|
After some experimentation, discussions with Xen folks and pondering Linux
source code, it became clear that most versions of Xen require at least 18
slots available on the receive ring to send an event.
|
|
|
|
membar_* functions are defined only as compiler barriers on !MP
kernels, while we're trying to be conservative in our use of the
barriers. Barriers are placed only where loads and stores might
get reordered and it matters at the same time. Shared info page
operations are using atomic instructions on Linux, so they get
barriers as well.
|
|
contained the pointer it received from user land. usbioctl() has
to reset it, otherwise user supplied data is passed to free().
OK mpi@
|
|
ok deraadt@ krw@
|
|
than driver specific strings.
ok kettenis
|
|
instead of using magic numbers. No binary change.
Diff from Martin Natano.
ok deraadt@
|
|
Reported by Jonathon Sisson <openbsd at j3z ! org>, thanks!
|
|
native byte order. No behaviour change, as attach time
parameters are just hints, except thay this makes audioctl
output nicer if the device was never opened.
|
|
|
|
to the "Windows Precision Touchpad" standard. when a compatible
device is found, hidmt claims all report ids and switches the device
into multitouch packet mode.
add imt, an i2c-HID driver that sits between ihidev and hidmt
|
|
establish interrupt before probing for devices to handle each report id
sign an int, found by jsg
|
|
code from FreeBSD, name from NetBSD
|
|
|
|
A crash reported by Jonathon Sisson is caused by incorrect calculation
of available descriptors on the tx ring. While here, split the mbuf
chain so that we won't unload the whole thing in the txeof before
removing grant table references from transmit descriptors.
|
|
When testing evtchn_mask bits we need to treat the array as a bit
matrix for an isset macro to test correct bits. Reported by reyk@
some time ago, Wei Liu <wei ! liu2 at citrix !com> figured out how
to reproduce the problem. Thanks!
|
|
|
|
|
|
Reyk has reported an issue that turned out to be an incorrect calculation
of bytes available for reading. This diff also places missed semaphore
releases in the xs_start and makes 'left' a size_t in xs_ring_{get,put}.
|