From: Rusty Russell <rusty@rustcorp.com.au>
To: Zachary Amsden <zach@vmware.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: proposed interface change for setting the ldt
Date: Sat, 19 Aug 2006 14:32:07 +1000 [thread overview]
Message-ID: <1155961927.9203.19.camel@localhost.localdomain> (raw)
In-Reply-To: <44E68857.6040806@vmware.com>
On Fri, 2006-08-18 at 20:41 -0700, Zachary Amsden wrote:
> Chris Wright wrote:
> > * Zachary Amsden (zach@vmware.com) wrote:
> >
> >> The paravirt-op just got a lot harder to implement, so there is a cost
> >> to the simpler interface.
> >>
> >
> > I'm missing why it's a lot harder. Seems reasonably straight forward.
> > puzzled...
> >
>
> Before it could be a direct call for us. Now I am forced to write a
> wrapper function around it which does exactly the same work as the
> native code, them calls a ROM function. It is straight forward, but
> obviously undesirable.
It sounds fine to me, although I'd like to see the patch. I don't have
anything against higher-level abstractions, if it helps any hypervisor,
as long as it doesn't warp the kernel code. And if most hypervisors and
native break it down the same way, well, we can always create helpers.
Cheers,
Rusty.
--
Help! Save Australia from the worst of the DMCA: http://linux.org.au/law
next prev parent reply other threads:[~2006-08-19 4:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 10:42 proposed interface change for setting the ldt Jeremy Fitzhardinge
2006-08-18 12:46 ` Jeremy Fitzhardinge
2006-08-18 13:03 ` Jeremy Fitzhardinge
2006-08-18 20:23 ` Zachary Amsden
2006-08-19 2:39 ` Jeremy Fitzhardinge
2006-08-19 3:12 ` Zachary Amsden
2006-08-19 3:18 ` Jeremy Fitzhardinge
2006-08-19 3:22 ` Chris Wright
2006-08-19 3:41 ` Zachary Amsden
2006-08-19 4:32 ` Rusty Russell [this message]
2006-08-19 12:18 ` Jeremy Fitzhardinge
2006-08-21 5:01 ` 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=1155961927.9203.19.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=chrisw@sous-sol.org \
--cc=virtualization@lists.osdl.org \
--cc=zach@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).