From: Zachary Amsden <zach@vmware.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Chris Wright <chrisw@sous-sol.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: rough sketch of revised patching infrastructure
Date: Thu, 22 Feb 2007 14:14:12 -0800 [thread overview]
Message-ID: <45DE15B4.9060109@vmware.com> (raw)
In-Reply-To: <45DDDD50.80502@goop.org>
Jeremy Fitzhardinge wrote:
> Rusty Russell wrote:
>
>> Actually, your paravirt_patch_insns has similar logic anyway, so this
>> code could collapse (it should fall back to paravirt_patch_default tho
>> IMHO).
>>
>>
>
> I wanted to get rid of the table because its now sparse, and possibly
> fairly large (since the special save flags & disable is at offset
> 0x80). And a switch would be pretty clean anyway.
>
> How does this look? Compiles, but untested.
>
That's looking pretty spiffy, if you ask me.
Zach
next prev parent reply other threads:[~2007-02-22 22:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 2:09 rough sketch of revised patching infrastructure Jeremy Fitzhardinge
2007-02-22 3:43 ` Rusty Russell
2007-02-22 10:22 ` Jeremy Fitzhardinge
2007-02-22 10:55 ` Rusty Russell
2007-02-22 18:13 ` Jeremy Fitzhardinge
2007-02-22 22:14 ` Zachary Amsden [this message]
2007-02-22 22:49 ` Jeremy Fitzhardinge
2007-02-22 22:51 ` Ian Campbell
2007-02-22 22:54 ` Jeremy Fitzhardinge
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=45DE15B4.9060109@vmware.com \
--to=zach@vmware.com \
--cc=chrisw@sous-sol.org \
--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).