All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	qemu-ppc Mailing List <qemu-ppc@nongnu.org>,
	Alexander Graf <agraf@suse.de>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 3/3] Give ivshmem its own config option
Date: Tue, 24 Feb 2015 19:57:11 +1100	[thread overview]
Message-ID: <20150224085711.GT4536@voom.redhat.com> (raw)
In-Reply-To: <CAEgOgz5QJohyeo0jcYogq=Xwmqkb4cWKaP_9Tq7L7yGhSed8mA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1510 bytes --]

On Mon, Feb 23, 2015 at 10:38:06PM -0800, Peter Crosthwaite wrote:
> On Mon, Feb 23, 2015 at 3:05 PM, David Gibson
> <david@gibson.dropbear.id.au> wrote:
> > Currently the ivshmem device is built whenever both PCI and KVM support are
> > included.  This patch gives it its own config option to allow easier
> > customization of whether to include it.  It's enabled by default in the
> > same circumstances as now - when both PCI and KVM are available.
> >
> > Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> > ---
> >  default-configs/pci.mak | 1 +
> >  hw/misc/Makefile.objs   | 4 +---
> >  2 files changed, 2 insertions(+), 3 deletions(-)
> >
> > diff --git a/default-configs/pci.mak b/default-configs/pci.mak
> > index bea6b01..58a2c0a 100644
> > --- a/default-configs/pci.mak
> > +++ b/default-configs/pci.mak
> > @@ -35,3 +35,4 @@ CONFIG_SDHCI=y
> >  CONFIG_EDU=y
> >  CONFIG_VGA=y
> >  CONFIG_VGA_PCI=y
> > +CONFIG_IVSHMEM=$(CONFIG_KVM)
> 
> Does this create an order of definition requirement between the
> configs? I guess its ok as CONFIG_KVM is defined super-early but it
> seems to be avoided where one config def depends on another.

Actually, I don't think it does.  When "=" is used, rather than ":="
make variables are expanded when used, not when defined.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-02-24  9:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-23 23:04 [Qemu-devel] [PATCH 0/3] Add config options for some not-always-sensible devices David Gibson
2015-02-23 23:05 ` [Qemu-devel] [PATCH 1/3] Add specific config options for PCI-E bridges David Gibson
2015-02-24  6:17   ` Peter Crosthwaite
2015-02-24  8:55     ` David Gibson
2015-02-24 16:44       ` Peter Crosthwaite
2015-02-24 16:38     ` Eric Blake
2015-02-23 23:05 ` [Qemu-devel] [PATCH 2/3] Create specific config option for "platform-bus" David Gibson
2015-02-24  6:27   ` Peter Crosthwaite
2015-02-24  8:57     ` David Gibson
2015-02-26  8:26       ` Peter Crosthwaite
2015-02-23 23:05 ` [Qemu-devel] [PATCH 3/3] Give ivshmem its own config option David Gibson
2015-02-24  6:38   ` Peter Crosthwaite
2015-02-24  8:57     ` David Gibson [this message]
2015-02-26  8:29       ` Peter Crosthwaite

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=20150224085711.GT4536@voom.redhat.com \
    --to=david@gibson.dropbear.id.au \
    --cc=agraf@suse.de \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.crosthwaite@xilinx.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.