From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Tim Deegan <Tim.Deegan@citrix.com>, Paolo Bonzini <pbonzini@redhat.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: [PATCH] HVM guests are allowed to use the entire virtual address space for
Date: Mon, 26 Jul 2010 11:57:30 +0100 [thread overview]
Message-ID: <C87328AA.1B979%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <20100726100006.GT13291@whitby.uk.xensource.com>
On 26/07/2010 11:00, "Tim Deegan" <Tim.Deegan@citrix.com> wrote:
> At 10:52 +0100 on 26 Jul (1280141550), Paolo Bonzini wrote:
>> On 05/25/2010 04:49 PM, Tim Deegan wrote:
>>> whatever they want, without any Xen hole. __addr_ok() is therefore
>>> always true for such guests.
>>>
>>> Signed-off-by: Tim Deegan <Tim.Deegan@citrix.com>
>>
>> Sorry for picking up yet another old patch after two months. :)
>>
>> Do you have a testcase for this or the other patch in the thread?
>
> I'm afraid not - this was a very old patch that had been gathering dust
> at the bottom of the XenServer code base. Calling
> e.g. GNTTABOP_setup_table from inside a HVM guest with the frame_list
> argument somewhere in the Xen virtual address space should trigger it,
> though.
The patch never got applied (to xen-unstable) by the way. We agreed on
xen-unstable:21456, which was a more targeted bug fix.
-- Keir
> Cheers,
>
> Tim.
prev parent reply other threads:[~2010-07-26 10:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 14:49 [PATCH] HVM guests are allowed to use the entire virtual address space for Tim Deegan
2010-05-25 15:04 ` Keir Fraser
2010-05-25 15:11 ` Keir Fraser
2010-05-25 15:14 ` Tim Deegan
2010-05-25 16:24 ` Keir Fraser
2010-07-26 9:52 ` Paolo Bonzini
2010-07-26 10:00 ` Tim Deegan
2010-07-26 10:57 ` Keir Fraser [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=C87328AA.1B979%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Tim.Deegan@citrix.com \
--cc=pbonzini@redhat.com \
--cc=xen-devel@lists.xensource.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).