From: Zachary Amsden <zach@vmware.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Andrew Morton <akpm@osdl.org>, Petr Vandrovec <petr@vmware.com>,
Chaz Masden <zamsden@gmail.com>,
Virtualization Mailing List <virtualization@lists.osdl.org>,
Chris Wright <chrisw@sous-sol.org>, Andi Kleen <ak@muc.de>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [RFC, PATCH 4/5] Paravirt_ops drop internal patches.patch
Date: Thu, 19 Apr 2007 22:13:29 -0700 [thread overview]
Message-ID: <46284BF9.8070103@vmware.com> (raw)
In-Reply-To: <46284B49.9080804@goop.org>
Jeremy Fitzhardinge wrote:
> Zachary Amsden wrote:
>
>> Some of these boot hooks do not need to be patched, in fact, it is better not
>> to patch them at all and thus keep them totally private.
>>
>>
>
> I think I generally backed off on patching init functions and the like.
> Are these really the only ones which need adjustment? I bet things like
> the descriptor functions could be indirect/private with very little impact.
>
Perhaps, but I'd rather not split hairs on it just yet - I actually have
no idea exactly which paravirt-ops will be needed, and so far, my
conclusions have led me to believe that a fare bit more than the obvious
paravirt-ops need to be available to modules. So I would rather just
split off pure init functions, which really have no business being
exported to modules.
Zach
prev parent reply other threads:[~2007-04-20 5:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 1:52 [RFC, PATCH 4/5] Paravirt_ops drop internal patches.patch Zachary Amsden
2007-04-20 5:10 ` Jeremy Fitzhardinge
2007-04-20 5:13 ` Zachary Amsden [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=46284BF9.8070103@vmware.com \
--to=zach@vmware.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=jeremy@goop.org \
--cc=mingo@elte.hu \
--cc=petr@vmware.com \
--cc=virtualization@lists.osdl.org \
--cc=zamsden@gmail.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 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.