From: Dushyant Bansal <cs5070214@cse.iitd.ac.in>
To: kvm-ppc@vger.kernel.org
Subject: Re: Patching instructions with PV versions
Date: Wed, 02 Mar 2011 16:46:01 +0000 [thread overview]
Message-ID: <4D6E7179.10109@cse.iitd.ac.in> (raw)
In-Reply-To: <4D68EC7D.3040100@cse.iitd.ac.in>
On Monday 28 February 2011 07:43 PM, Sethi Varun-B16395 wrote:
> Hi Dushyant,
> Please refer to the magic page section of the following document:
> linux/Documentation/kvm/ppc-pv.txt
>
Thanks, now I do have a better understanding.
> Regards
> Varun
> ________________________________________
> From: kvm-ppc-owner@vger.kernel.org [kvm-ppc-owner@vger.kernel.org] on behalf of Dushyant Bansal [cs5070214@cse.iitd.ac.in]
> Sent: Saturday, February 26, 2011 5:35 PM
> To: kvm-ppc@vger.kernel.org
> Subject: Patching instructions with PV versions
>
> Hi,
> I understand that in order to improve performance by reducing vm
> exits, kvm uses one shared page between kvm and guest. Now, guest can
> map this page and access its fields using load, store instructions.
> Then, it patches instructions with their paravirtualized versions
> (inside kvm_use_magic_page). I have a few questions.
> Is patching, by default enabled for every guest?
> When is this patching done? Does it target only guest kernel code?
>
> Thanks,
> Dushyant
> --
> To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2011-03-02 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-26 12:17 Patching instructions with PV versions Dushyant Bansal
2011-02-28 14:13 ` Sethi Varun-B16395
2011-03-02 16:46 ` Dushyant Bansal [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=4D6E7179.10109@cse.iitd.ac.in \
--to=cs5070214@cse.iitd.ac.in \
--cc=kvm-ppc@vger.kernel.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