From: Steven Smith <sos22-xen@srcf.ucam.org>
To: Jeremy Katz <katzj@redhat.com>
Cc: aliguori <aliguori@mail.utexas.edu>,
xen-devel <xen-devel@lists.xensource.com>,
sos22@srcf.ucam.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH] Paravirt framebuffer frontend kernel support [1/5]
Date: Wed, 6 Sep 2006 10:11:41 +0100 [thread overview]
Message-ID: <20060906091140.GA3257@cam.ac.uk> (raw)
In-Reply-To: <1157472713.7571.87.camel@aglarond.local>
[-- Attachment #1.1: Type: text/plain, Size: 4494 bytes --]
> > There are still a couple of things from the last round which are
> > unfixed. This is mostly my fault for going on holiday at an
> > inconvenient time; sorry about that.
> We won't begrudge you a holiday -- hope it was a good one :-)
Yes, thank you.
> > The big problem with this is that you don't support shadow translate
> > mode guests, because the frontend exposes mfns directly to the
> > backend. The correct way of fixing this is to use grant tables, but,
> > as Anthony pointed out, that's quite hard due to the amount of memory
> > you need to grant access to.
> >
> > The easy way of doing this would be to just increase the size of the
> > grant tables. Alternatively, you could add support for granting
> > access to ranges of memory, but that sounds like a whole lot of work.
> >
> > You could also put in a quick hack of just translating the mfns in the
> > backend if the frontend is in shadow translate mode, but that's not
> > really very nice.
> I wouldn't complain if we go the route Keir suggested and have Xen do
> it ;-) But if not, I think that given the size of the memory in
> question + grant tables, the quick hack is probably going to be the
> "right" thing for this case.
Okay. Adding translations to the hypervisor isn't going to happen
until after 3.0.3, so we should probably just leave this for a little
while.
> > > diff -r 5fa9b746d24f -r 510c6bceb87f linux-2.6-xen-sparse/arch/i386/kernel/setup-xen.c
> > > --- a/linux-2.6-xen-sparse/arch/i386/kernel/setup-xen.c Sat Sep 02 12:11:54 2006 +0100
> > > +++ b/linux-2.6-xen-sparse/arch/i386/kernel/setup-xen.c Sat Sep 02 15:11:17 2006 -0400
> > > @@ -1866,8 +1866,12 @@ void __init setup_arch(char **cmdline_p)
> > > #endif
> > > #endif
> > > } else {
> > > +#if defined(CONFIG_VT) && defined(CONFIG_DUMMY_CONSOLE)
> > > + conswitchp = &dummy_con;
> > > +#else
> > > extern int console_use_vt;
> > > console_use_vt = 0;
> > > +#endif
> > > }
> > > }
> > Not quite sure I understand what this is trying to achieve, or why it's
> > related to the PV framebuffer stuff.
> It makes it so that console switching is achieved by the dummy console
> and then when the fbcon driver is loaded, it takes over.
Okay.
>
> [snip]
> > Perhaps XEN_KEYBOARD should depend on XEN_FRAMEBUFFER, given that it
> > doesn't work without it.
> Yeah, seems reasonable enough -- I've added to my tree.
Thanks.
> > > config XEN_SCRUB_PAGES
> > > bool "Scrub memory before freeing it to Xen"
> > > default y
> > > diff -r 5fa9b746d24f -r 510c6bceb87f linux-2.6-xen-sparse/drivers/xen/Makefile
> > > --- a/linux-2.6-xen-sparse/drivers/xen/Makefile Sat Sep 02 12:11:54 2006 +0100
> > > +++ b/linux-2.6-xen-sparse/drivers/xen/Makefile Sat Sep 02 15:11:17 2006 -0400
> > > @@ -15,3 +15,5 @@ obj-$(CONFIG_XEN_NETDEV_FRONTEND) += net
> > > obj-$(CONFIG_XEN_NETDEV_FRONTEND) += netfront/
> > > obj-$(CONFIG_XEN_PCIDEV_BACKEND) += pciback/
> > > obj-$(CONFIG_XEN_PCIDEV_FRONTEND) += pcifront/
> > > +obj-$(CONFIG_XEN_FRAMEBUFFER) += xenfb/
> > > +obj-$(CONFIG_XEN_KEYBOARD) += xenkbd/
> > > diff -r 5fa9b746d24f -r 510c6bceb87f linux-2.6-xen-sparse/mm/memory.c
> > > --- a/linux-2.6-xen-sparse/mm/memory.c Sat Sep 02 12:11:54 2006 +0100
> > > +++ b/linux-2.6-xen-sparse/mm/memory.c Sat Sep 02 15:11:17 2006 -0400
> > > @@ -881,6 +881,7 @@ unsigned long zap_page_range(struct vm_a
> > > tlb_finish_mmu(tlb, address, end);
> > > return end;
> > > }
> > > +EXPORT_SYMBOL(zap_page_range);
> > It's unfortunate that we have to modify an upstream file here, but I
> > can't really see any alternative.
> Well, if we don't allow the framebuffer to be modular then it doesn't
> have to be exported. But that also seems like the wrong answer :-)
Yeah, adding the EXPORT_SYMBOL is the right thing to do here, it's
just kind of annoying. Oh well.
>
> > > +#if 0
> > > + /* if we're not set up to use graphics mode, then don't initialize */
> > > + if (xenbus_scanf(XBT_NIL, "console", "use_graphics", "%d", &ret) < 0)
> > > + return -ENODEV;
> > > + if (ret == 0)
> > > + return -ENODEV;
> > > +#endif
> > That's interesting. What is this here for?
> It looks like it got accidentally #if 0'd while merging patches.
> Whoops. Basically, if the guest isn't set up to use a graphical
> console, then we shouldn't initialize the devices.
That seems like a good idea. Please put this back in.
Steven.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-09-06 9:11 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 [this message]
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
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=20060906091140.GA3257@cam.ac.uk \
--to=sos22-xen@srcf.ucam.org \
--cc=aliguori@mail.utexas.edu \
--cc=armbru@redhat.com \
--cc=katzj@redhat.com \
--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.