Hi,
But this is independent of WHQL certification. My understanding is
that Microsoft will only allow the owner of the PCI Vendor ID to WHQL
drivers. As best as I know, this is not a publicly documented
process.
Do you have any examples of anyone else successfuling WHQL'ing drivers
by
On Tue, 16 Sep 2014 08:27:40 +0800
Amos Kong ak...@redhat.com wrote:
Set timeout to 10:
non-smp guest with quick backend (1.2M/s) - about 490K/s)
That sounds like an awful lot. This is a 60% loss in throughput.
I don't think we can live with that.
--
Michael
signature.asc
Description:
Amos Kong ak...@redhat.com writes:
On Sun, Sep 14, 2014 at 01:12:58AM +0800, Amos Kong wrote:
On Thu, Sep 11, 2014 at 09:08:03PM +0930, Rusty Russell wrote:
Amos Kong ak...@redhat.com writes:
When I check hwrng attributes in sysfs, cat process always gets
stuck if guest has only 1 vcpu
Michael S. Tsirkin m...@redhat.com writes:
On Fri, Sep 12, 2014 at 10:58:03AM +0930, Rusty Russell wrote:
Michael S. Tsirkin m...@redhat.com writes:
On Thu, Sep 11, 2014 at 10:26:52AM +0930, Rusty Russell wrote:
Hi all,
Probably won't read mail. Linus, I'll have pull requests
On Wed, Sep 17, 2014 at 01:23:46AM +0930, Rusty Russell wrote:
Michael S. Tsirkin m...@redhat.com writes:
On Fri, Sep 12, 2014 at 10:58:03AM +0930, Rusty Russell wrote:
Michael S. Tsirkin m...@redhat.com writes:
On Thu, Sep 11, 2014 at 10:26:52AM +0930, Rusty Russell wrote:
Hi all,
virtio_ring currently sends the device (usually a hypervisor)
physical addresses of its I/O buffers. This is okay when DMA
addresses and physical addresses are the same thing, but this isn't
always the case. For example, this never works on Xen guests, and
it is likely to fail if a physical
On non-PPC systems, virtio_pci should use the DMA API. This fixes
virtio_pci on Xen. On PPC, using the DMA API would break things, so
we need to preserve the old behavior.
The big comment in this patch explains the considerations in more
detail.
Signed-off-by: Andy Lutomirski
This fixes virtio on Xen guests as well as on any other platform
that uses virtio_pci on which physical addresses don't match bus
addresses.
This can be tested with:
virtme-run --xen xen --kimg arch/x86/boot/bzImage --console
using virtme from here:
Now that virtio supports real DMA, drivers should play by the rules.
For virtio_net, that means that DMA should be done to and from
dynamically-allocated memory, not the kernel stack.
This should have no effect on any performance-critical code paths.
Signed-off-by: Andy Lutomirski
