From: Avi Kivity <avi@redhat.com>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: Gleb Natapov <gleb@redhat.com>,
kvm@vger.kernel.org, Carsten Otte <cotte@de.ibm.com>,
"Zhang, Xiantao" <xiantao.zhang@intel.com>
Subject: Re: [PATCH 1/4] Introduce kvm_vcpu_is_bsp() function.
Date: Mon, 08 Jun 2009 19:57:22 +0300 [thread overview]
Message-ID: <4A2D42F2.7000301@redhat.com> (raw)
In-Reply-To: <1244480017.16253.27.camel@slate.austin.ibm.com>
Hollis Blanchard wrote:
>> please wrap with HAVE_KVM_IRQCHIP (which is a close approximation).
>>
>
> I don't know about that... I've definitely thought about implementing an
> in-kernel PIC for PowerPC. (That will make more sense as an optimization
> once the processors with hypervisor support start hitting the market.)
>
Yes, wasn't such a great idea. I guess a new symbol
CONFIG_KVM_APIC_ARCHITECTURE which will also encapsulate the ioapic stuff.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-06-08 16:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 9:32 [PATCH 0/4] decouple vcpu index from apic id Gleb Natapov
2009-06-08 9:32 ` [PATCH 1/4] Introduce kvm_vcpu_is_bsp() function Gleb Natapov
2009-06-08 11:20 ` Avi Kivity
2009-06-08 16:53 ` Hollis Blanchard
2009-06-08 16:57 ` Avi Kivity [this message]
2009-06-09 1:00 ` Zhang, Xiantao
2009-06-09 3:35 ` Avi Kivity
2009-06-08 9:32 ` [PATCH 2/4] Use pointer to vcpu instead of vcpu_id in timer code Gleb Natapov
2009-06-08 9:32 ` [PATCH 3/4] Break dependency between vcpu index in vcpus array and vcpu_id Gleb Natapov
2009-06-08 11:23 ` Avi Kivity
2009-06-08 9:32 ` [PATCH 4/4] Use macro to iterate over vcpus Gleb Natapov
2009-06-08 11:25 ` [PATCH 0/4] decouple vcpu index from apic id Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2009-06-09 2:30 Zhang, Xiantao
2009-06-09 2:30 ` Zhang, Xiantao
2009-06-09 5:26 ` Gleb Natapov
2009-06-09 5:26 ` Gleb Natapov
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=4A2D42F2.7000301@redhat.com \
--to=avi@redhat.com \
--cc=cotte@de.ibm.com \
--cc=gleb@redhat.com \
--cc=hollisb@us.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=xiantao.zhang@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 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.