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 14:40:49 -0700 [thread overview]
Message-ID: <46366261.3070901@vmware.com> (raw)
In-Reply-To: <46365A0F.9040901@goop.org>
Jeremy Fitzhardinge wrote:
> I think the more things we can devolve out of paravirt_ops the better,
> especially if they make well-defined self-contained interfaces of their
> own. I would be open, for example, to moving all the pagetable and
> privileged instruction operations out into their own _ops interfaces
> (but not right now).
>
I think this trend of moving things into smaller compact interfaces is
the right way to go, and certainly the apic stuff can devolve, as well
as privileged / pagetable ops. We can target that for .23, and it would
go quite a ways towards giving a better foundation for x86_64 (even
non-x86) paravirt to build on.
Zach
next prev parent reply other threads:[~2007-04-30 21:40 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
2007-04-30 21:05 ` Jeremy Fitzhardinge
2007-04-30 21:40 ` Zachary Amsden [this message]
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=46366261.3070901@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 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.