From: Zachary Amsden <zach@vmware.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: virtualization@lists.osdl.org,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: huh startup_ipi_hook?
Date: Mon, 30 Apr 2007 13:35:10 -0700 [thread overview]
Message-ID: <463652FE.9080604@vmware.com> (raw)
In-Reply-To: <46363B5D.7060101@goop.org>
Jeremy Fitzhardinge wrote:
> Zachary Amsden wrote:
>
>> Of course we can create a bunch of new code to use the genapic
>> interface. It is just a matter of copying apic.c and io-apic.c
>> verbatim and applying the sed command s/apic/vmi_apic/g.
>>
>
> Wouldn't it be cleaner to just change apic.c and io-apic.c to use, say,
> apic_ops to get access to the actual hardware, and then you could have
> native and vmi versions while sharing the bulk of the code. Isn't that
> what genapic is intended to solve anyway?
>
But the native and vmi versions would be identical. You would be moving
the apic_read / apic_write operations from paravirt_ops to apic_ops,
which doesn't really solve anything, it just moves it around.
Zach
next prev parent reply other threads:[~2007-04-30 20:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 7:14 huh startup_ipi_hook? Eric W. Biederman
2007-04-28 7:22 ` Jeremy Fitzhardinge
2007-04-28 8:06 ` Eric W. Biederman
2007-04-28 8:26 ` Jeremy Fitzhardinge
2007-04-28 8:42 ` Eric W. Biederman
2007-04-28 8:59 ` Jeremy Fitzhardinge
2007-04-30 18:33 ` Zachary Amsden
2007-04-30 18:54 ` Jeremy Fitzhardinge
2007-04-30 20:35 ` Zachary Amsden [this message]
2007-04-30 21:05 ` Jeremy Fitzhardinge
2007-04-30 21:40 ` Zachary Amsden
2007-04-28 8:45 ` Andi Kleen
2007-04-28 9:05 ` Eric W. Biederman
2007-04-30 20:30 ` 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=463652FE.9080604@vmware.com \
--to=zach@vmware.com \
--cc=ebiederm@xmission.com \
--cc=jeremy@goop.org \
--cc=virtualization@lists.osdl.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;
as well as URLs for NNTP newsgroup(s).