[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200922095158-mutt-send-email-mst@kernel.org>
Date: Tue, 22 Sep 2020 09:52:12 -0400
From: "Michael S. Tsirkin" <mst@...hat.com>
To: Christian Borntraeger <borntraeger@...ibm.com>
Cc: Pierre Morel <pmorel@...ux.ibm.com>, linux-kernel@...r.kernel.org,
pasic@...ux.ibm.com, frankja@...ux.ibm.com, jasowang@...hat.com,
cohuck@...hat.com, kvm@...r.kernel.org, linux-s390@...r.kernel.org,
virtualization@...ts.linux-foundation.org, thomas.lendacky@....com,
david@...son.dropbear.id.au, linuxram@...ibm.com,
hca@...ux.ibm.com, gor@...ux.ibm.com
Subject: Re: [PATCH v12 0/2] s390: virtio: let arch validate VIRTIO features
Will do for the next Linux.
On Tue, Sep 22, 2020 at 02:15:17PM +0200, Christian Borntraeger wrote:
> Michael,
>
> are you going to pick this series?
>
>
> On 10.09.20 10:53, Pierre Morel wrote:
> > Hi all,
> >
> > The goal of the series is to give a chance to the architecture
> > to validate VIRTIO device features.
> >
> > I changed VIRTIO_F_IOMMU_PLATFORM to VIRTIO_F_ACCESS_PLATFORM
> > I forgot in drivers/virtio/Kconfig, and put back the inclusion
> > of virtio_config.h for the definition of the callback in
> > arch/s390/mm/init.c I wrongly removed in the last series.
> >
> > Regards,
> > Pierre
> >
> >
> > Pierre Morel (2):
> > virtio: let arch advertise guest's memory access restrictions
> > s390: virtio: PV needs VIRTIO I/O device protection
> >
> > arch/s390/Kconfig | 1 +
> > arch/s390/mm/init.c | 11 +++++++++++
> > drivers/virtio/Kconfig | 6 ++++++
> > drivers/virtio/virtio.c | 15 +++++++++++++++
> > include/linux/virtio_config.h | 10 ++++++++++
> > 5 files changed, 43 insertions(+)
> >
Powered by blists - more mailing lists