From: Alex Williamson <alex.williamson@redhat.com>
To: Kirti Wankhede <kwankhede@nvidia.com>
Cc: <cjia@nvidia.com>, <linux-kernel@vger.kernel.org>, <kvm@vger.kernel.org>
Subject: Re: [PATCH] vfio-mdev: Fix mtty sample driver building
Date: Thu, 15 Dec 2016 01:12:18 -0700 [thread overview]
Message-ID: <20161215011218.1103e435@t450s.home> (raw)
In-Reply-To: <ed9971c9-2f2c-c40d-c37b-bbc4353b836e@nvidia.com>
On Thu, 15 Dec 2016 13:15:34 +0530
Kirti Wankhede <kwankhede@nvidia.com> wrote:
> On 12/15/2016 1:09 AM, Alex Williamson wrote:
> > This sample driver was originally under Documentation/ and was moved
> > to samples, but build support was never adjusted for the new location.
> >
> > Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> > ---
> > samples/Kconfig | 7 +++++++
> > samples/Makefile | 3 ++-
> > samples/vfio-mdev/Makefile | 14 +-------------
> > 3 files changed, 10 insertions(+), 14 deletions(-)
> >
>
> This change would bring this example driver in Kernel build system if
> selected. I do have verified build and tested it on x86_64 platform.
> Have you verified x86 and PPC/ARM build (which I think primarily could
> use VFIO)?
I have not, but I'm fairly confident that CONFIG_SAMPLES is not a
typical user or distro config option, so I think we're at a low risk
of breaking anyone. In general I test almost exclusively for x86_64 and
rely on external auto builders to identify issues on other archs.
Thanks,
Alex
> > diff --git a/samples/Kconfig b/samples/Kconfig
> > index a6d2a43..b124f62 100644
> > --- a/samples/Kconfig
> > +++ b/samples/Kconfig
> > @@ -105,4 +105,11 @@ config SAMPLE_BLACKFIN_GPTIMERS
> > help
> > Build samples of blackfin gptimers sample module.
> >
> > +config SAMPLE_VFIO_MDEV_MTTY
> > + tristate "Build VFIO mtty example mediated device sample code -- loadable modules only"
> > + depends on VFIO_MDEV_DEVICE && m
> > + help
> > + Build a virtual tty sample driver for use as a VFIO
> > + mediated device
> > +
> > endif # SAMPLES
> > diff --git a/samples/Makefile b/samples/Makefile
> > index e17d66d..86a137e 100644
> > --- a/samples/Makefile
> > +++ b/samples/Makefile
> > @@ -2,4 +2,5 @@
> >
> > obj-$(CONFIG_SAMPLES) += kobject/ kprobes/ trace_events/ livepatch/ \
> > hw_breakpoint/ kfifo/ kdb/ hidraw/ rpmsg/ seccomp/ \
> > - configfs/ connector/ v4l/ trace_printk/ blackfin/
> > + configfs/ connector/ v4l/ trace_printk/ blackfin/ \
> > + vfio-mdev/
> > diff --git a/samples/vfio-mdev/Makefile b/samples/vfio-mdev/Makefile
> > index a932edb..cbbd868 100644
> > --- a/samples/vfio-mdev/Makefile
> > +++ b/samples/vfio-mdev/Makefile
> > @@ -1,13 +1 @@
> > -#
> > -# Makefile for mtty.c file
> > -#
> > -KERNEL_DIR:=/lib/modules/$(shell uname -r)/build
> > -
> > -obj-m:=mtty.o
> > -
> > -modules clean modules_install:
> > - $(MAKE) -C $(KERNEL_DIR) SUBDIRS=$(PWD) $@
> > -
> > -default: modules
> > -
> > -module: modules
> > +obj-$(CONFIG_SAMPLE_VFIO_MDEV_MTTY) += mtty.o
> >
next prev parent reply other threads:[~2016-12-15 8:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 19:39 Alex Williamson
2016-12-15 7:45 ` Kirti Wankhede
2016-12-15 8:12 ` Alex Williamson [this message]
2016-12-15 9:47 ` Kirti Wankhede
2016-12-15 17:09 ` Alex Williamson
2016-12-15 9:36 ` Auger Eric
2016-12-15 17:08 ` 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=20161215011218.1103e435@t450s.home \
--to=alex.williamson@redhat.com \
--cc=cjia@nvidia.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®