similar to: Proposal for virtio standardization.

On Mon, Mar 31, 2014 at 02:22:50PM +1030, Rusty Russell wrote: > > It's head of my virtio-next tree. Hey Rusty, While we have your attention --- what's your opinion about adding TRIM support to virtio-blk. I understand that you're starting an OASIS standardization process for virtio --- what does that mean vis-a-vis a patch to plumb discard support through virtio-blk?

On Mon, Mar 31, 2014 at 02:22:50PM +1030, Rusty Russell wrote: > > It's head of my virtio-next tree. Hey Rusty, While we have your attention --- what's your opinion about adding TRIM support to virtio-blk. I understand that you're starting an OASIS standardization process for virtio --- what does that mean vis-a-vis a patch to plumb discard support through virtio-blk?

On Wed, Sep 20, 2017 at 09:11:57AM +0000, Liang, Cunming wrote: > Hi Michael, > > > -----Original Message----- > > From: virtio-dev at lists.oasis-open.org [mailto:virtio-dev at lists.oasis-open.org] > > On Behalf Of Michael S. Tsirkin > > Sent: Sunday, September 10, 2017 1:06 PM > > To: virtio-dev at lists.oasis-open.org > > Cc: virtualization at

On Wed, Sep 20, 2017 at 09:11:57AM +0000, Liang, Cunming wrote: > Hi Michael, > > > -----Original Message----- > > From: virtio-dev at lists.oasis-open.org [mailto:virtio-dev at lists.oasis-open.org] > > On Behalf Of Michael S. Tsirkin > > Sent: Sunday, September 10, 2017 1:06 PM > > To: virtio-dev at lists.oasis-open.org > > Cc: virtualization at

On Wed, 10 Apr 2019 10:03:01 -0400 (EDT) Pankaj Gupta <pagupta at redhat.com> wrote: > > > > On Wed, Apr 10, 2019 at 09:38:22AM +0530, Pankaj Gupta wrote: > > > This patch adds virtio-pmem driver for KVM guest. > > > > > > Guest reads the persistent memory range information from > > > Qemu over VIRTIO and registers it on nvdimm_bus. It

On Wed, 10 Apr 2019 10:03:01 -0400 (EDT) Pankaj Gupta <pagupta at redhat.com> wrote: > > > > On Wed, Apr 10, 2019 at 09:38:22AM +0530, Pankaj Gupta wrote: > > > This patch adds virtio-pmem driver for KVM guest. > > > > > > Guest reads the persistent memory range information from > > > Qemu over VIRTIO and registers it on nvdimm_bus. It

Since virtio is an OASIS standard draft now, virtio implementation discussions are taking place on the virtio-dev OASIS mailing list. Update MAINTAINERS. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- MAINTAINERS | 3 + drivers/net/virtio_net.c | 355 +++++++++++++++++++++++++---------------------- 2 files changed, 191 insertions(+), 167 deletions(-) diff --git

Since virtio is an OASIS standard draft now, virtio implementation discussions are taking place on the virtio-dev OASIS mailing list. Update MAINTAINERS. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- MAINTAINERS | 3 + drivers/net/virtio_net.c | 355 +++++++++++++++++++++++++---------------------- 2 files changed, 191 insertions(+), 167 deletions(-) diff --git

On Mon, Jun 03, 2013 at 09:56:15AM +0930, Rusty Russell wrote: > "Michael S. Tsirkin" <mst at redhat.com> writes: > > On Thu, May 30, 2013 at 08:53:45AM -0500, Anthony Liguori wrote: > >> Rusty Russell <rusty at rustcorp.com.au> writes: > >> > >> > Anthony Liguori <aliguori at us.ibm.com> writes: > >> >> Forcing a

On Mon, Jun 03, 2013 at 09:56:15AM +0930, Rusty Russell wrote: > "Michael S. Tsirkin" <mst at redhat.com> writes: > > On Thu, May 30, 2013 at 08:53:45AM -0500, Anthony Liguori wrote: > >> Rusty Russell <rusty at rustcorp.com.au> writes: > >> > >> > Anthony Liguori <aliguori at us.ibm.com> writes: > >> >> Forcing a

On Wed, Feb 08, 2017 at 02:37:57PM +0100, Christian Borntraeger wrote: > On 02/08/2017 04:20 AM, Michael S. Tsirkin wrote: > [...] > > * Prototype > > > > A partial prototype can be found under > > tools/virtio/ringtest/ring.c > > > > Test run: > > [mst at tuck ringtest]$ time ./ring > > real 0m0.399s > > user 0m0.791s > >

On Wed, Feb 08, 2017 at 02:37:57PM +0100, Christian Borntraeger wrote: > On 02/08/2017 04:20 AM, Michael S. Tsirkin wrote: > [...] > > * Prototype > > > > A partial prototype can be found under > > tools/virtio/ringtest/ring.c > > > > Test run: > > [mst at tuck ringtest]$ time ./ring > > real 0m0.399s > > user 0m0.791s > >

On Mon, Nov 28, 2016 at 01:56:04AM +0000, Gonglei (Arei) wrote: > Hi Michael, > > Thanks for your feedback firstly! > > > -----Original Message----- > > From: virtio-dev at lists.oasis-open.org [mailto:virtio-dev at lists.oasis-open.org] > > On Behalf Of Michael S. Tsirkin > > Sent: Sunday, November 27, 2016 11:33 AM > > To: Gonglei (Arei) > >

On Mon, Nov 28, 2016 at 01:56:04AM +0000, Gonglei (Arei) wrote: > Hi Michael, > > Thanks for your feedback firstly! > > > -----Original Message----- > > From: virtio-dev at lists.oasis-open.org [mailto:virtio-dev at lists.oasis-open.org] > > On Behalf Of Michael S. Tsirkin > > Sent: Sunday, November 27, 2016 11:33 AM > > To: Gonglei (Arei) > >

Dear List: I have installed the lastest Samba 3.0 onto an AMD 2.6 GHz RedHat 9.0 system running mirrored SCSI drives. The system is multi homed as such:- eth0 - 192.168.50.5 - 192.168.100.199 eth1 - public IP address I connect from an XP Home box to a Samba share via the 192.168.1.0/24 subnet, mapped as Drive Z and performed the following file transfers. Samba (Z:) -> Samba (Z:)

On Mon, Oct 10, 2016 at 05:59:03PM +0100, Will Deacon wrote: > On Fri, Oct 07, 2016 at 07:24:34AM +0300, Michael S. Tsirkin wrote: > > On Tue, Sep 27, 2016 at 09:57:14AM +0100, Will Deacon wrote: > > > Hi Michael, > > > > > > In commit 1a937693993f ("virtio: new feature to detect IOMMU device quirk"), > > > you added a new feature bit

On Mon, Oct 10, 2016 at 05:59:03PM +0100, Will Deacon wrote: > On Fri, Oct 07, 2016 at 07:24:34AM +0300, Michael S. Tsirkin wrote: > > On Tue, Sep 27, 2016 at 09:57:14AM +0100, Will Deacon wrote: > > > Hi Michael, > > > > > > In commit 1a937693993f ("virtio: new feature to detect IOMMU device quirk"), > > > you added a new feature bit

On Wed, Jun 06, 2018 at 03:44:11PM +0300, Michael S. Tsirkin wrote: > On Wed, Jun 06, 2018 at 08:11:54PM +0800, Tiwei Bie wrote: > > On Tue, Jun 05, 2018 at 03:23:11PM +0300, Michael S. Tsirkin wrote: > > > On Tue, Jun 05, 2018 at 09:36:53AM +0800, Tiwei Bie wrote: > > > > On Mon, Jun 04, 2018 at 07:32:25PM +0300, Michael S. Tsirkin wrote: > > > > > On

As result deprecation of MSI-X/MSI enablement functions pci_enable_msix() and pci_enable_msi_block() all drivers using these two interfaces need to be updated to use the new pci_enable_msi_range() and pci_enable_msix_range() interfaces. Signed-off-by: Alexander Gordeev <agordeev at redhat.com> Cc: Rusty Russell <rusty at rustcorp.com.au> Cc: "Michael S. Tsirkin" <mst at

As result deprecation of MSI-X/MSI enablement functions pci_enable_msix() and pci_enable_msi_block() all drivers using these two interfaces need to be updated to use the new pci_enable_msi_range() and pci_enable_msix_range() interfaces. Signed-off-by: Alexander Gordeev <agordeev at redhat.com> Cc: Rusty Russell <rusty at rustcorp.com.au> Cc: "Michael S. Tsirkin" <mst at