From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Tim Deegan <tim@xen.org>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: Re: [RFC PATCH 6/16]: PVH xen: Define pvh guest and header changes..
Date: Thu, 24 Jan 2013 17:56:16 -0800 [thread overview]
Message-ID: <20130124175616.62876e3f@mantra.us.oracle.com> (raw)
In-Reply-To: <20130124153431.GF20551@ocelot.phlegethon.org>
On Thu, 24 Jan 2013 15:34:31 +0000
Tim Deegan <tim@xen.org> wrote:
> At 17:51 -0800 on 11 Jan (1357926698), Mukesh Rathor wrote:
> > diff -r fadb3f2f5d97 -r 5af39353f3f9
> > xen/include/asm-x86/guest_access.h ---
> > a/xen/include/asm-x86/guest_access.h Fri Jan 11 16:25:27
> > 2013 -0800 +++ b/xen/include/asm-x86/guest_access.h Fri Jan
> > 11 16:27:46 2013 -0800 @@ -14,27 +14,27 @@
> > /* Raw access functions: no type checking. */
> > #define raw_copy_to_guest(dst, src, len) \
> > + (is_hvm_or_pvh_vcpu(current) ? \
> > copy_to_user_hvm((dst), (src), (len)) : \
> > __copy_to_user((dst), (src), (len)))
> > #define __raw_copy_from_guest(dst, src, len) \
> > - (is_hvm_vcpu(current) ? \
> > + (is_hvm_or_pvh_vcpu(current) ? \
> > copy_from_user_hvm((dst), (src), (len)) : \
> > __copy_from_user((dst), (src), (len)))
> > #define __raw_clear_guest(dst, len) \
> > - (is_hvm_vcpu(current) ? \
> > + (is_hvm_or_pvh_vcpu(current) ? \
> > clear_user_hvm((dst), (len)) : \
> > clear_user((dst), (len)))
>
> Please don't mess up these nicely aligned backslashes. :)
Ooopsy!! My bad. Fixed.
prev parent reply other threads:[~2013-01-25 1:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 1:51 [RFC PATCH 6/16]: PVH xen: Define pvh guest and header changes Mukesh Rathor
2013-01-14 11:38 ` Jan Beulich
2013-01-16 0:37 ` Mukesh Rathor
2013-01-16 9:53 ` Jan Beulich
2013-01-31 1:21 ` Mukesh Rathor
2013-01-24 15:34 ` Tim Deegan
2013-01-25 1:56 ` Mukesh Rathor [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=20130124175616.62876e3f@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=Xen-devel@lists.xensource.com \
--cc=tim@xen.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).