From: Wei Liu <wei.liu2@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: Ross Lagerwall <ross.lagerwall@citrix.com>,
xen-devel@lists.xensource.com, Wei Liu <wei.liu2@citrix.com>,
Paul Durrant <Paul.Durrant@citrix.com>
Subject: Re: [PATCH v2 25/24] xl: Document VGA problems arising from lack of physmap dmop
Date: Fri, 6 Oct 2017 15:58:52 +0100 [thread overview]
Message-ID: <20171006145852.4d5gwajcgfcbfg72@citrix.com> (raw)
In-Reply-To: <22999.39365.432042.895432@mariner.uk.xensource.com>
On Fri, Oct 06, 2017 at 03:57:09PM +0100, Ian Jackson wrote:
> Wei Liu writes ("Re: [PATCH v2 25/24] xl: Document VGA problems arising from lack of physmap dmop"):
> > On Fri, Oct 06, 2017 at 03:33:52PM +0100, Ian Jackson wrote:
> > > [ extra patch, following test report from Ross ]
> ...
> > > +Domains with stdvga graphics cards to not work.
> > > +Domains with cirrus vga do work,
> > > +but there are performance problems with the vga console.
> > > +
> >
> > I don't follow. Do you imply cirrus doesn't need add_to_physmap to
> > function?
>
> Evidently not. My qemu-dm-debian.guest.osstest.log does not contain
> any of the errors Ross quotes and I can connect to my guest's VGA
> console over vnc.
>
> It does take a little extra time to boot, I think. I didn't really
> notice this and thought it was a side effect of the happenstance that
> my guest had been converted from PV...
>
Let's just say they don't work properly yet?
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-10-06 14:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 14:33 [PATCH v2 25/24] xl: Document VGA problems arising from lack of physmap dmop Ian Jackson
2017-10-06 14:51 ` Wei Liu
2017-10-06 14:54 ` Ross Lagerwall
2017-10-06 14:54 ` Paul Durrant
2017-10-06 15:01 ` Ian Jackson
2017-10-06 16:35 ` Paul Durrant
2017-10-06 14:57 ` Ian Jackson
2017-10-06 14:58 ` Wei Liu [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=20171006145852.4d5gwajcgfcbfg72@citrix.com \
--to=wei.liu2@citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=ross.lagerwall@citrix.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.