From: Steve Ofsthun <sofsthun@virtualiron.com>
To: Robert Phillips <rsp.vi.xen@gmail.com>
Cc: zhu <vanbas.han@gmail.com>, xen-devel@lists.xensource.com
Subject: Re: [PATCH - proposed] XI Shadow Page Table Mechanism]
Date: Fri, 30 Jun 2006 09:33:19 -0400 [thread overview]
Message-ID: <44A5281F.5090407@virtualiron.com> (raw)
In-Reply-To: <fc060d960606300618t1edd553sdfcf30d26c94458c@mail.gmail.com>
Robert Phillips wrote:
> Yes, that's true. If the caller supplied a bogus PFN (one larger than
> ram size), we'd crash.
> BTW, we are avoiding use of grant table transfers because they fragment
> PSE pages.
> -- rsp
We also avoid grant table transfers due to incompatibilities with QEMU's one
time map of all of guest memory. If you use grant table transfers (via
netfront/netback), the QEMU memory map quickly becomes out of date. Any
QEMU I/O (net, or disk), will result in stale guest data being used.
> On 6/30/06, *zhu* <vanbas.han@gmail.com <mailto:vanbas.han@gmail.com>>
> wrote:
>
> I'm afraid it could trigger some certain problems only when you open l2
> PSE flag and use grant table to transfer pages between domains. I'm not
> very sure about it. :-)
>
> _______________________________________________________
> Best Regards,
> hanzhu
>
>
> Robert Phillips 写道:
> > Hi Han,
> > You are right again. I have not seen this cause a problem but we'll
> > certainly fix it.
> > -- rsp
> >
> > On 6/29/06, zhu < vanbas.han@gmail.com
> <mailto:vanbas.han@gmail.com>> wrote:
> >>
> >> Hi, Robert,
> >> I found out another confusing code snippet:
> >> in void xi_invl_mfn(struct domain *d, unsigned long mfn)
> >> if (ext && pfn < ext->large_page_aligned_size)
> >>
> >> According to the code, it should be
> >> if (ext && (pfn>>SPT_ENTRIES_ORDER) <
> ext->large_page_aligned_size)
> >>
> >> If I made any mistake, please point it out.
> >> _______________________________________________________
> >> Best Regards,
> >> hanzhu
> >>
> >
> >
>
>
>
>
> --
> --------------------------------------------------------------------
> Robert S. Phillips Virtual Iron Software
> rphillips@virtualiron.com
> <mailto:rphillips@virtualiron.com> Tower 1, Floor 2
> 978-849-1220 900 Chelmsford Street
> Lowell, MA 01851
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
--
Steve Ofsthun - Virtual Iron Software, Inc.
next prev parent reply other threads:[~2006-06-30 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44A3CA74.4000206@virtualiron.com>
[not found] ` <44A3D3CE.3040408@virtualiron.com>
[not found] ` <44A3E08B.9090103@gmail.com>
[not found] ` <44A3E98B.9040602@virtualiron.com>
[not found] ` <44A3F073.50305@virtualiron.com>
2006-06-30 2:37 ` [PATCH - proposed] XI Shadow Page Table Mechanism] zhu
2006-06-30 12:24 ` Robert Phillips
[not found] ` <44A51DE9.1020909@gmail.com>
2006-06-30 13:18 ` Robert Phillips
2006-06-30 13:33 ` Steve Ofsthun [this message]
2006-06-30 13:47 ` zhu
[not found] ` <44A52215.8050505@virtualiron.com>
2006-07-01 9:22 ` zhu
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=44A5281F.5090407@virtualiron.com \
--to=sofsthun@virtualiron.com \
--cc=rsp.vi.xen@gmail.com \
--cc=vanbas.han@gmail.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 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.