similar to: VIRTIO_F_IOMMU_PLATFORM

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 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 (VIRTIO_F_IOMMU_PLATFORM) to describe whether > > or not a given virtio device requires

> -----Original Message----- > From: Stefan Hajnoczi [mailto:stefanha at redhat.com] > Sent: Friday, June 1, 2018 5:00 PM > To: Liu, Changpeng <changpeng.liu at intel.com> > Cc: virtualization at lists.linux-foundation.org; cavery at redhat.com; > jasowang at redhat.com; pbonzini at redhat.com; Wang, Wei W > <wei.w.wang at intel.com> > Subject: Re: [PATCH v4]

> -----Original Message----- > From: Stefan Hajnoczi [mailto:stefanha at redhat.com] > Sent: Friday, June 1, 2018 5:00 PM > To: Liu, Changpeng <changpeng.liu at intel.com> > Cc: virtualization at lists.linux-foundation.org; cavery at redhat.com; > jasowang at redhat.com; pbonzini at redhat.com; Wang, Wei W > <wei.w.wang at intel.com> > Subject: Re: [PATCH v4]

Commits: fd2a0437dc33 virtio_net: introduce virtio_net_hdr_{from,to}_skb e858fae2b0b8 virtio_net: use common code for virtio_net_hdr and skb GSO conversion introduced a subtle (but unexplained) difference in how virtio_net flags are derived from skb->ip_summed fields on transmit from the guest to the host/backend. Prior to the patches the flags would be set to VIRTIO_NET_HDR_F_NEEDS_CSUM if

Commits: fd2a0437dc33 virtio_net: introduce virtio_net_hdr_{from,to}_skb e858fae2b0b8 virtio_net: use common code for virtio_net_hdr and skb GSO conversion introduced a subtle (but unexplained) difference in how virtio_net flags are derived from skb->ip_summed fields on transmit from the guest to the host/backend. Prior to the patches the flags would be set to VIRTIO_NET_HDR_F_NEEDS_CSUM if

> -----Original Message----- > From: Stefan Hajnoczi [mailto:stefanha at redhat.com] > Sent: Thursday, May 31, 2018 6:31 PM > To: Liu, Changpeng <changpeng.liu at intel.com> > Cc: virtualization at lists.linux-foundation.org; cavery at redhat.com; > jasowang at redhat.com; pbonzini at redhat.com; Wang, Wei W > <wei.w.wang at intel.com> > Subject: Re: [PATCH v4]

> -----Original Message----- > From: Stefan Hajnoczi [mailto:stefanha at redhat.com] > Sent: Thursday, May 31, 2018 6:31 PM > To: Liu, Changpeng <changpeng.liu at intel.com> > Cc: virtualization at lists.linux-foundation.org; cavery at redhat.com; > jasowang at redhat.com; pbonzini at redhat.com; Wang, Wei W > <wei.w.wang at intel.com> > Subject: Re: [PATCH v4]

On Tue, Jan 10, 2017 at 05:51:18PM +0000, Robin Murphy wrote: > From: Will Deacon <will.deacon at arm.com> > > Booting Linux on an ARM fastmodel containing an SMMU emulation results > in an unexpected I/O page fault from the legacy virtio-blk PCI device: > > [ 1.211721] arm-smmu-v3 2b400000.smmu: event 0x10 received: > [ 1.211800] arm-smmu-v3 2b400000.smmu:

On Tue, Jan 10, 2017 at 05:51:18PM +0000, Robin Murphy wrote: > From: Will Deacon <will.deacon at arm.com> > > Booting Linux on an ARM fastmodel containing an SMMU emulation results > in an unexpected I/O page fault from the legacy virtio-blk PCI device: > > [ 1.211721] arm-smmu-v3 2b400000.smmu: event 0x10 received: > [ 1.211800] arm-smmu-v3 2b400000.smmu:

On Wed, Jan 11, 2017 at 2:01 AM, Will Deacon <will.deacon at arm.com> wrote: > On Wed, Jan 11, 2017 at 01:33:31AM +0200, Michael S. Tsirkin wrote: >> On Tue, Jan 10, 2017 at 05:51:18PM +0000, Robin Murphy wrote: >> > From: Will Deacon <will.deacon at arm.com> >> > >> > Booting Linux on an ARM fastmodel containing an SMMU emulation results >>

On Wed, Jan 11, 2017 at 2:01 AM, Will Deacon <will.deacon at arm.com> wrote: > On Wed, Jan 11, 2017 at 01:33:31AM +0200, Michael S. Tsirkin wrote: >> On Tue, Jan 10, 2017 at 05:51:18PM +0000, Robin Murphy wrote: >> > From: Will Deacon <will.deacon at arm.com> >> > >> > Booting Linux on an ARM fastmodel containing an SMMU emulation results >>

On Wed, Jan 11, 2017 at 10:01:39AM +0000, Will Deacon wrote: > On Wed, Jan 11, 2017 at 01:33:31AM +0200, Michael S. Tsirkin wrote: > > On Tue, Jan 10, 2017 at 05:51:18PM +0000, Robin Murphy wrote: > > > From: Will Deacon <will.deacon at arm.com> > > > > > > Booting Linux on an ARM fastmodel containing an SMMU emulation results > > > in an

On Wed, Jan 11, 2017 at 10:01:39AM +0000, Will Deacon wrote: > On Wed, Jan 11, 2017 at 01:33:31AM +0200, Michael S. Tsirkin wrote: > > On Tue, Jan 10, 2017 at 05:51:18PM +0000, Robin Murphy wrote: > > > From: Will Deacon <will.deacon at arm.com> > > > > > > Booting Linux on an ARM fastmodel containing an SMMU emulation results > > > in an

On Fri, Jan 13, 2017 at 09:25:22AM +0000, Will Deacon wrote: > On Fri, Jan 13, 2017 at 12:12:56AM +0200, Michael S. Tsirkin wrote: > > On Wed, Jan 11, 2017 at 10:01:39AM +0000, Will Deacon wrote: > > > On Wed, Jan 11, 2017 at 01:33:31AM +0200, Michael S. Tsirkin wrote: > > > > On Tue, Jan 10, 2017 at 05:51:18PM +0000, Robin Murphy wrote: > > > > > From:

On Fri, Jan 13, 2017 at 09:25:22AM +0000, Will Deacon wrote: > On Fri, Jan 13, 2017 at 12:12:56AM +0200, Michael S. Tsirkin wrote: > > On Wed, Jan 11, 2017 at 10:01:39AM +0000, Will Deacon wrote: > > > On Wed, Jan 11, 2017 at 01:33:31AM +0200, Michael S. Tsirkin wrote: > > > > On Tue, Jan 10, 2017 at 05:51:18PM +0000, Robin Murphy wrote: > > > > > From:

On Thu, May 31, 2018 at 11:53:26PM +0000, Liu, Changpeng wrote: > > > > -----Original Message----- > > From: Stefan Hajnoczi [mailto:stefanha at redhat.com] > > Sent: Thursday, May 31, 2018 6:31 PM > > To: Liu, Changpeng <changpeng.liu at intel.com> > > Cc: virtualization at lists.linux-foundation.org; cavery at redhat.com; > > jasowang at

On 04/06/2018 06:14, Liu, Changpeng wrote: >>> But I believe the specification says VIRTIO_BLK_T_OUT means direction, so >>> OR the two bits together should compliance with the specification. >> I cannot find that in the specification: >> >> http://docs.oasis-open.org/virtio/virtio/v1.0/cs04/virtio-v1.0-cs04.html#x1- >> 2020002 >> >> and it

This patch series is the follow up on the discussions we had before about the RFC titled [RFC,V2] virtio: Add platform specific DMA API translation for virito devices (https://patchwork.kernel.org/patch/10417371/). There were suggestions about doing away with two different paths of transactions with the host/QEMU, first being the direct GPA and the other being the DMA API based translations.