Re: [Qemu-devel] [PATCH V3] e1000: Handle IO Port.

2011-07-22 Thread Anthony PERARD
On Tue, Jul 19, 2011 at 14:41, Juan Quintela quint...@redhat.com wrote: Anthony PERARD anthony.per...@citrix.com wrote: This patch introduces the two IOPorts on e1000, IOADDR and IODATA. The IOADDR is used to specify which register we want to access when we read or write on IODATA. This

Re: [Qemu-devel] [PATCH V3] e1000: Handle IO Port.

2011-07-19 Thread Juan Quintela
Anthony PERARD anthony.per...@citrix.com wrote: This patch introduces the two IOPorts on e1000, IOADDR and IODATA. The IOADDR is used to specify which register we want to access when we read or write on IODATA. This patch fixes some weird behavior that I see when I use e1000 with QEMU/Xen,

Re: [Qemu-devel] [PATCH V3] e1000: Handle IO Port.

2011-07-18 Thread Anthony PERARD
On Sat, Jul 2, 2011 at 18:35, Andreas Färber andreas.faer...@web.de wrote: Am 30.06.2011 um 23:35 schrieb Anthony PERARD: This patch introduces the two IOPorts on e1000, IOADDR and IODATA. The IOADDR is used to specify which register we want to access when we read or write on IODATA. This

Re: [Qemu-devel] [PATCH V3] e1000: Handle IO Port.

2011-07-02 Thread Andreas Färber
Am 30.06.2011 um 23:35 schrieb Anthony PERARD: This patch introduces the two IOPorts on e1000, IOADDR and IODATA. The IOADDR is used to specify which register we want to access when we read or write on IODATA. This patch fixes some weird behavior that I see when I use e1000 with QEMU/Xen,

[Qemu-devel] [PATCH V3] e1000: Handle IO Port.

2011-06-30 Thread Anthony PERARD
This patch introduces the two IOPorts on e1000, IOADDR and IODATA. The IOADDR is used to specify which register we want to access when we read or write on IODATA. This patch fixes some weird behavior that I see when I use e1000 with QEMU/Xen, the guest memory can be corrupted by this NIC because