From: Ravikiran Thirumalai <kiran@scalemp.com>
To: Glauber Costa <glommer@gmail.com>
Cc: ehabkost@redhat.com, shai@scalemp.com,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Glauber Costa <gcosta@redhat.com>,
chrisw@sous-sol.org, anthony@codemonkey.ws,
Ingo Molnar <mingo@elte.hu>,
virtualization@lists.linux-foundation.org, tglx@linutronix.de,
ak@suse.de
Subject: Re: [PATCH 4/5] [PATCH] introduce paravirt helpers
Date: Tue, 19 Feb 2008 11:59:52 -0800 [thread overview]
Message-ID: <20080219195951.GU6209@localdomain> (raw)
In-Reply-To: <5d6222a80802171256l6e178eb8h1080bfd5a6b95ef3@mail.gmail.com>
On Sun, Feb 17, 2008 at 06:56:56PM -0200, Glauber Costa wrote:
>On Feb 17, 2008 4:05 PM, Ingo Molnar <mingo@elte.hu> wrote:
>>
>> * Glauber Costa <gcosta@redhat.com> wrote:
>>
>> > config X86_VSMP
>> > bool "Support for ScaleMP vSMP"
>> > depends on X86_64 && PCI
>> > - help
>> > + select PARAVIRT
>> > + help
>>
>> hm, what's the idea here?
>
>guys from scalemp can probably give a better picture if needed,
>but in a nutshell, there are two aspects involved with the vsmp
>support. The first one
>is special L1 alignments, and the second, specialized irq handling routines.
>
>Only the second one is paravirt in itself, and are the ones addressed
>in this patch.
>The specialized routines now goes through paravirt ops. So when using
>a vsmp machine,
>paravirt has to be selected, in order to enable such functions.
Thanks Glauber. Well put.
That said, future revs of vSMP will have the ability to work optimally even
without the paravirtualized irq ops. This is an upcoming feature, and did not
exist when we tested the paravirt ops 2-3 months ago. So, it will be
better, now, not to select PARAVIRT while selecting X86_VSMP. Then,
CONFIG_VSMP will just select the cacheline padding to be used and PARAVIRT
will be needed if irq operations need to be paravirtualized.
I shall submit a patch to that effect.
Thanks,
Kiran
prev parent reply other threads:[~2008-02-19 19:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1202757365-18634-1-git-send-email-gcosta@redhat.com>
2008-02-11 19:16 ` [PATCH 2/5] [PATCH] make vsmp_init void, instead of static int Glauber Costa
[not found] ` <1202757365-18634-2-git-send-email-gcosta@redhat.com>
2008-02-11 19:16 ` [PATCH 3/5] [PATCH] call vsmp_init explicitly Glauber Costa
[not found] ` <1202757365-18634-3-git-send-email-gcosta@redhat.com>
2008-02-11 19:16 ` [PATCH 4/5] [PATCH] introduce paravirt helpers Glauber Costa
2008-02-17 18:04 ` [PATCH 3/5] [PATCH] call vsmp_init explicitly Ingo Molnar
[not found] ` <1202757365-18634-4-git-send-email-gcosta@redhat.com>
2008-02-11 19:16 ` [PATCH 5/5] [PATCH] use the paravirt helpers Glauber Costa
2008-02-17 18:05 ` [PATCH 4/5] [PATCH] introduce " Ingo Molnar
2008-02-17 20:56 ` Glauber Costa
[not found] ` <5d6222a80802171256l6e178eb8h1080bfd5a6b95ef3@mail.gmail.com>
2008-02-19 19:59 ` Ravikiran Thirumalai [this message]
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=20080219195951.GU6209@localdomain \
--to=kiran@scalemp.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=anthony@codemonkey.ws \
--cc=chrisw@sous-sol.org \
--cc=ehabkost@redhat.com \
--cc=gcosta@redhat.com \
--cc=glommer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=shai@scalemp.com \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.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