From: Markus Armbruster <armbru@redhat.com>
To: Steven Smith <sos22@cam.ac.uk>
Cc: aliguori <aliguori@mail.utexas.edu>,
Jeremy Katz <katzj@redhat.com>,
xen-devel <xen-devel@lists.xensource.com>,
sos22@srcf.ucam.org
Subject: Re: [PATCH] Paravirt framebuffer frontend kernel support [1/5]
Date: Thu, 02 Nov 2006 08:53:38 +0100 [thread overview]
Message-ID: <87ac3az3lp.fsf@pike.pond.sub.org> (raw)
In-Reply-To: <20060910093801.GA1874@cam.ac.uk> (Steven Smith's message of "Sun, 10 Sep 2006 10:38:01 +0100")
Steven Smith <sos22@cam.ac.uk> writes:
[...]
>> As far as I can see, this is our only option right now. I'm ignorant
>> of `shadow translate mode'; can somebody please educate me on how to
>> detect and translate shadow translate mode frontend mfns in the
>> backend?
> Shadow translate mode is a mode of the shadow page tables in which Xen
> does machine<->physical address translations on behalf of the guest.
> It's mostly used for HVM guests to give them the impression of a
> mostly-contiguous block of memory starting at machine address 0.
>
> If you just bung the guest-supplied machine frame numbers through
> xc_translate_gpfn_list you should be fine. That does the translation
> if you're in shadow translate mode and does nothing if you're not.
Assuming you mean xc_domain_translate_gpfn_list(). I tried
translating fbdev_mfn right before use, as follows:
ret = xc_domain_translate_gpfn_list(xenfb->xc, domid, 1,
&fbdev_mfn, &fbdev_mfn);
if (ret < 0)
goto error;
xenfb->fb_info = xc_map_foreign_range(xenfb->xc, domid, XC_PAGE_SIZE,
PROT_READ | PROT_WRITE,
fbdev_mfn);
if (xenfb->fb_info == NULL)
goto error;
However, xc_domain_translate_gpfn_list() always fails with EINVAL for
me. If I read its code correctly, this can happen because op.nr_gpfns
is too large, or !shadow_mode_translate(). I suspect its the latter.
Should I call it only when in shadow translate mode? How to check for
that? Or am I doing something wrong?
next prev parent reply other threads:[~2006-11-02 7:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-02 19:58 [PATCH] Paravirt framebuffer frontend kernel support [1/5] Jeremy Katz
2006-09-04 9:00 ` Steven Smith
2006-09-04 14:03 ` Keir Fraser
2006-09-05 16:11 ` Jeremy Katz
2006-09-06 9:11 ` Steven Smith
2006-09-06 15:56 ` Keir Fraser
2006-09-21 18:41 ` Markus Armbruster
2006-09-21 19:29 ` Keir Fraser
2006-09-21 19:33 ` Steven Smith
2006-09-10 7:39 ` Markus Armbruster
2006-09-10 9:38 ` Steven Smith
2006-09-30 8:52 ` Markus Armbruster
2006-11-02 10:10 ` Markus Armbruster
2006-11-02 10:36 ` Ewan Mellor
2006-11-02 12:34 ` Markus Armbruster
2006-11-02 16:19 ` Steven Smith
2006-11-02 16:31 ` Ewan Mellor
2006-11-03 14:18 ` Markus Armbruster
2006-11-03 17:01 ` Steven Smith
2006-11-02 15:02 ` Markus Armbruster
2006-11-02 15:38 ` Ewan Mellor
2006-11-02 7:53 ` Markus Armbruster [this message]
2006-11-02 7:58 ` Keir Fraser
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=87ac3az3lp.fsf@pike.pond.sub.org \
--to=armbru@redhat.com \
--cc=aliguori@mail.utexas.edu \
--cc=katzj@redhat.com \
--cc=sos22@cam.ac.uk \
--cc=sos22@srcf.ucam.org \
--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.