From: Avi Kivity <avi@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 2/4] sipi and init: move common code
Date: Mon, 08 Jun 2009 18:48:38 +0300 [thread overview]
Message-ID: <4A2D32D6.9040304@redhat.com> (raw)
In-Reply-To: <20090608155253.GA11966@poweredge.glommer>
Glauber Costa wrote:
> On Mon, Jun 08, 2009 at 12:08:17PM +0300, Avi Kivity wrote:
>
>> Glauber Costa wrote:
>>
>>> provide functions to query and reset the state of sipi and
>>> init in cpu's apic. This way we can move the kvm specific functions
>>> out of the apic path.
>>>
>>>
>>>
>> The new functions and data members are kvm specific. Please update
>> their names to reflect that. 'sipi_needed' would be really confusing
>> for someone reading the code from a tcg perspective (it's confusing even
>> from a kvm perspective, but that's our problem and can be addressed
>> later).
>>
> The idea of such series is exactly to write it in a way that is _not_
> kvm specific, although kvm is the only user. So, I may change the
> name if you prefer, but I would not like to introduce any "kvm" string
> on it. To do that, we might as well stick with what we have.
>
Well, sipi_needed is certainly kvm specific, if you look at its usage.
I don't see how anything else could use it.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-06-08 15:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 21:19 [PATCH 0/4] apic/ioapic kvm free implementation Glauber Costa
2009-06-03 21:19 ` [PATCH 1/4] avoid halted state for in kernel irqchip Glauber Costa
2009-06-03 21:19 ` [PATCH 2/4] sipi and init: move common code Glauber Costa
2009-06-03 21:19 ` [PATCH 3/4] provide a kvm-free implementation of apic Glauber Costa
2009-06-03 21:19 ` [PATCH 4/4] provide a kvm-free implementation of ioapic Glauber Costa
2009-06-08 9:08 ` [PATCH 2/4] sipi and init: move common code Avi Kivity
2009-06-08 15:52 ` Glauber Costa
2009-06-08 15:48 ` Avi Kivity [this message]
2009-06-08 16:43 ` Glauber Costa
2009-06-04 15:04 ` [PATCH 0/4] apic/ioapic kvm free implementation Gleb Natapov
2009-06-04 19:46 ` Jan Kiszka
2009-06-04 20:02 ` Gleb Natapov
-- strict thread matches above, loose matches on Subject: below --
2009-06-03 18:25 [PATCH 0/4] kvm free implementation of apic/ioapic Glauber Costa
2009-06-03 18:25 ` [PATCH 1/4] avoid halted state for in kernel irqchip Glauber Costa
2009-06-03 18:25 ` [PATCH 2/4] sipi and init: move common code Glauber Costa
2009-06-03 19:53 ` Gleb Natapov
2009-06-03 21:11 ` Glauber Costa
2009-06-02 19:37 [PATCH 0/4] Provide kvm-free implementations of apic/ioapic Glauber Costa
2009-06-02 19:37 ` [PATCH 1/4] always halt non-bsp cpu Glauber Costa
2009-06-02 19:37 ` [PATCH 2/4] sipi and init: move common code Glauber Costa
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=4A2D32D6.9040304@redhat.com \
--to=avi@redhat.com \
--cc=glommer@redhat.com \
--cc=kvm@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