public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Krowiak <akrowiak@linux.ibm.com>
To: Christoph Hellwig <hch@lst.de>,
	Alex Williamson <alex.williamson@redhat.com>,
	Kirti Wankhede <kwankhede@nvidia.com>
Cc: Halil Pasic <pasic@linux.ibm.com>,
	Jason Herne <jjherne@linux.ibm.com>,
	Zhenyu Wang <zhenyuw@linux.intel.com>,
	Zhi Wang <zhi.a.wang@intel.com>,
	kvm@vger.kernel.org, linux-s390@vger.kernel.org,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/4] vfio-mdev: allow building the samples into the kernel
Date: Tue, 10 Jan 2023 09:54:51 -0500	[thread overview]
Message-ID: <b317380e-26bf-b478-4aea-0355e0de4017@linux.ibm.com> (raw)
In-Reply-To: <20230110091009.474427-2-hch@lst.de>


On 1/10/23 4:10 AM, Christoph Hellwig wrote:
> There is nothing in the vfio-mdev sample drivers that requires building
> them as modules, so remove that restriction.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
>   samples/Kconfig | 16 ++++++++--------
>   1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/samples/Kconfig b/samples/Kconfig
> index 0d81c00289ee36..f1b8d4ff123036 100644
> --- a/samples/Kconfig
> +++ b/samples/Kconfig
> @@ -184,23 +184,23 @@ config SAMPLE_UHID
>   	  Build UHID sample program.
>   
>   config SAMPLE_VFIO_MDEV_MTTY
> -	tristate "Build VFIO mtty example mediated device sample code -- loadable modules only"
> -	depends on VFIO_MDEV && m
> +	tristate "Build VFIO mtty example mediated device sample code"
> +	depends on VFIO_MDEV


Admittedly, I'm not very fluent with Kconfig, but in patch 2 you stated, 
"VFIO_MDEV is just a library with helpers for the drivers. Stop making 
it a user choice and just select it by the drivers that use the 
helpers". Why are you not selecting it here?


>   	help
>   	  Build a virtual tty sample driver for use as a VFIO
>   	  mediated device
>   
>   config SAMPLE_VFIO_MDEV_MDPY
> -	tristate "Build VFIO mdpy example mediated device sample code -- loadable modules only"
> -	depends on VFIO_MDEV && m
> +	tristate "Build VFIO mdpy example mediated device sample code"
> +	depends on VFIO_MDEV
>   	help
>   	  Build a virtual display sample driver for use as a VFIO
>   	  mediated device.  It is a simple framebuffer and supports
>   	  the region display interface (VFIO_GFX_PLANE_TYPE_REGION).
>   
>   config SAMPLE_VFIO_MDEV_MDPY_FB
> -	tristate "Build VFIO mdpy example guest fbdev driver -- loadable module only"
> -	depends on FB && m
> +	tristate "Build VFIO mdpy example guest fbdev driver"
> +	depends on FB
>   	select FB_CFB_FILLRECT
>   	select FB_CFB_COPYAREA
>   	select FB_CFB_IMAGEBLIT
> @@ -208,8 +208,8 @@ config SAMPLE_VFIO_MDEV_MDPY_FB
>   	  Guest fbdev driver for the virtual display sample driver.
>   
>   config SAMPLE_VFIO_MDEV_MBOCHS
> -	tristate "Build VFIO mdpy example mediated device sample code -- loadable modules only"
> -	depends on VFIO_MDEV && m
> +	tristate "Build VFIO mdpy example mediated device sample code"
> +	depends on VFIO_MDEV
>   	select DMA_SHARED_BUFFER
>   	help
>   	  Build a virtual display sample driver for use as a VFIO

  reply	other threads:[~2023-01-10 14:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10  9:10 misc mdev tidyups Christoph Hellwig
2023-01-10  9:10 ` [PATCH 1/4] vfio-mdev: allow building the samples into the kernel Christoph Hellwig
2023-01-10 14:54   ` Anthony Krowiak [this message]
2023-01-10 15:27     ` Christoph Hellwig
2023-01-10 15:32       ` Anthony Krowiak
2023-01-10 16:11   ` Jason Gunthorpe
2023-01-10  9:10 ` [PATCH 2/4] vfio-mdev: turn VFIO_MDEV into a selectable symbol Christoph Hellwig
2023-01-10 14:51   ` Anthony Krowiak
2023-01-10 16:12   ` Jason Gunthorpe
2023-01-10  9:10 ` [PATCH 3/4] vfio-mdev: move the mtty usage documentation Christoph Hellwig
2023-01-10 16:12   ` Jason Gunthorpe
2023-01-10  9:10 ` [PATCH 4/4] vfio-mdev: remove an non-existing driver from vfio-mediated-device Christoph Hellwig
2023-01-10 14:49   ` Anthony Krowiak
2023-01-10 16:13   ` Jason Gunthorpe
2023-01-23 19:37 ` misc mdev tidyups Alex Williamson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b317380e-26bf-b478-4aea-0355e0de4017@linux.ibm.com \
    --to=akrowiak@linux.ibm.com \
    --cc=alex.williamson@redhat.com \
    --cc=hch@lst.de \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jjherne@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwankhede@nvidia.com \
    --cc=linux-s390@vger.kernel.org \
    --cc=pasic@linux.ibm.com \
    --cc=zhenyuw@linux.intel.com \
    --cc=zhi.a.wang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox