From: Zachary Amsden <zach@vmware.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Petr Vandrovec <petr@vmware.com>,
nigel@nigel.suspend2.net, Arjan van de Ven <arjan@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: VMware, x86_64 and 2.6.21.
Date: Fri, 04 May 2007 14:04:42 -0700 [thread overview]
Message-ID: <463B9FEA.8@vmware.com> (raw)
In-Reply-To: <m13b2cpcr2.fsf@ebiederm.dsl.xmission.com>
Eric W. Biederman wrote:
> Is this linux running on vmware or vmware running on linux?
>
VMware running on Linux.
> This sounds like playing with fire. Although I suppose you could do it generally
> by making software irqs trigger a general protection fault.
>
Better if you don't have to; the whole point of the swirq is faster
handling.
> What we currently have is:
> int assign_irq_vector(int irq, cpumask_t);
>
> It has a number of interesting properties such as you can change
> the vector assignment at runtime, and we can migrate the irq
> between cpus.
>
Yes, but still not enough here.
> That is pretty much the architecture we have to support msi. Although
> irq != vector not even at a fixed offset.
>
It doesn't look like you can safely allocate an exclusive IRQ here
however - the IO-APIC could always route a hardware IRQ for the matching
vector right on top of you unless, I'm misreading something.
Zach
next prev parent reply other threads:[~2007-05-04 21:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 5:42 VMware, x86_64 and 2.6.21 Nigel Cunningham
2007-05-01 6:13 ` Jeff Chua
2007-05-01 6:33 ` Nigel Cunningham
2007-05-01 11:09 ` Jan Engelhardt
2007-05-01 12:51 ` Jeff Chua
2007-05-01 7:24 ` Michael Gerdau
2007-05-01 7:36 ` Nigel Cunningham
2007-05-01 11:10 ` Jan Engelhardt
2007-05-01 11:54 ` Nigel Cunningham
2007-05-01 13:46 ` Mark Lord
2007-05-01 15:09 ` Nigel Cunningham
2007-05-01 14:57 ` Arjan van de Ven
2007-05-01 15:14 ` Nigel Cunningham
2007-05-02 9:30 ` Petr Vandrovec
2007-05-04 11:40 ` Eric W. Biederman
2007-05-04 15:08 ` Zachary Amsden
2007-05-04 20:14 ` Eric W. Biederman
2007-05-04 21:04 ` Zachary Amsden [this message]
2007-05-05 9:56 ` Christoph Hellwig
2007-05-05 18:06 ` John Anthony Kazos Jr.
2007-05-06 7:16 ` Valdis.Kletnieks
2007-05-06 11:08 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2007-05-01 6:50 Marcos Pinto
2007-05-01 7:06 ` Nigel Cunningham
2007-05-01 22:38 ` Zachary Amsden
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=463B9FEA.8@vmware.com \
--to=zach@vmware.com \
--cc=arjan@infradead.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nigel@nigel.suspend2.net \
--cc=petr@vmware.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;
as well as URLs for NNTP newsgroup(s).