From: Paul Mackerras <paulus@samba.org>
To: Scott Wood <scottwood@freescale.com>
Cc: Alexander Graf <agraf@suse.de>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>,
Gleb Natapov <gleb@redhat.com>,
Stuart Yoder <stuart.yoder@freescale.com>
Subject: Re: [STRAWMAN PATCH] KVM: PPC: Add ioctl to specify interrupt controller architecture to emulate
Date: Fri, 15 Mar 2013 09:02:41 +1100 [thread overview]
Message-ID: <20130314220241.GH9841@iris.ozlabs.ibm.com> (raw)
In-Reply-To: <1363284935.28440.8@snotra>
On Thu, Mar 14, 2013 at 01:15:35PM -0500, Scott Wood wrote:
> On 03/13/2013 08:26:20 PM, Paul Mackerras wrote:
> >I arbitrarily
> >assigned 0x58494353 for KVM_CAP_IRQ_XICS as the args[0] value to
> >indicate XICS.
>
> Why is it called KVM_CAP_<whatever> if it's not a capability?
Because it's associated with a capability. I'm not wedded to the name.
> >I think it would be better if we don't have to get a
> >new capability number assigned every time we want to add a new type of
> >interrupt controller.
>
> How often does it really happen? If a simple enumeration is good
> enough for identifying the main IRQ controller device type, it
> should be good enough for identifying the vcpu irq arch.
Whatever. I really don't care at this point, I'm just getting
extremely tired of the bikeshedding. If you don't like it, propose
something.
Paul.
next prev parent reply other threads:[~2013-03-14 22:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 3:29 [STRAWMAN PATCH] KVM: PPC: Add ioctl to specify interrupt controller architecture to emulate Paul Mackerras
2013-03-07 14:00 ` Alexander Graf
2013-03-08 10:37 ` Paul Mackerras
2013-03-08 11:04 ` Alexander Graf
2013-03-09 2:26 ` Paul Mackerras
2013-03-11 9:15 ` Alexander Graf
2013-03-14 0:14 ` Scott Wood
2013-03-14 0:25 ` Alexander Graf
2013-03-14 1:26 ` Paul Mackerras
2013-03-14 18:15 ` Scott Wood
2013-03-14 22:02 ` Paul Mackerras [this message]
2013-03-14 22:44 ` Alexander Graf
2013-03-14 22:53 ` Scott Wood
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=20130314220241.GH9841@iris.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=agraf@suse.de \
--cc=gleb@redhat.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=scottwood@freescale.com \
--cc=stuart.yoder@freescale.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