All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mao Mingy <maomingya928@gmail.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xen.org,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: frame buffer shared by domains on arch arm linux
Date: Fri, 23 Jan 2015 18:03:50 +0800	[thread overview]
Message-ID: <54C21C86.5010006@gmail.com> (raw)
In-Reply-To: <1422005091.19859.3.camel@citrix.com>


On 23/01/2015 17:24, Ian Campbell wrote:
> On Fri, 2015-01-23 at 17:14 +0800, Mao Mingy wrote:
>> 1. QEMU's start up parameter, changed the original from Xen4.5
>> /usr/local/lib/xen/bin/qemu-system-i386 -xen-domid 0
> Are you trying to use pvfb for dom0's own graphical output?
No. I got it wrong. Right now writing to Dom0's frame buffer from Dom0 
is working.
I am trying to run the program on DomU to to write to frame buffer of 
guest DomU and it's not working
> This qemu process you quote here is running against dom0 in order to
> provide backend services for frontends running in dom0 itself, i.e.
> things like loopback qdisk mounts to the toolstack.
>
> For a domU the xl toolstack should be launching a new qemu process
> specifically for that domain, e.g. with -xen-domid <domid> (for
> domid!=0).
>
> Ian.
>
I modified the "-xen-domid" and "-name" of qemu-system-i386  to match 
the domain name and id of the guest Dom, the result is same.
The XENFB_TYPE_UPDATE event sent by guest Linux did NOT reach to QEMU 
side (xenfb_handle_events() of xenfb.c).
should it be processed here?

Thank you for the sharp thought and prompt reply.

Regards,
Mao Mingya

  reply	other threads:[~2015-01-23 10:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21  8:36 frame buffer shared by domains on arch arm linux Mao Mingy
2015-01-21 10:51 ` Stefano Stabellini
2015-01-22  2:18   ` Mao Mingy
2015-01-22 11:56     ` Stefano Stabellini
2015-01-23  9:14       ` Mao Mingy
2015-01-23  9:24         ` Ian Campbell
2015-01-23 10:03           ` Mao Mingy [this message]
2015-01-23 10:11             ` Ian Campbell
2015-01-23 10:23               ` Mao Mingy
2015-01-23 10:32                 ` Stefano Stabellini
     [not found]                   ` <CAFLc04ByJ0OEsqEeXcL3goaGiLkYFpwTnFrZnRfv2Tx463XwdA@mail.gmail.com>
     [not found]                     ` <alpine.DEB.2.02.1501231456260.18131@kaball.uk.xensource.com>
     [not found]                       ` <54C5DD03.5070406@gmail.com>
     [not found]                         ` <alpine.DEB.2.02.1501261049370.13428@kaball.uk.xensource.com>
     [not found]                           ` <54C741CC.8040604@gmail.com>
2015-01-27 10:24                             ` Stefano Stabellini
2015-01-27 10:55                               ` Ian Campbell
2015-01-23 10:34                 ` Ian Campbell
2015-01-23 10:48                   ` Mao Mingy
2015-01-23 10:56                     ` Ian Campbell
2015-01-23 13:13                       ` Mao Mingya
2015-01-23 13:16                         ` Ian Campbell
2015-01-26  6:06                       ` Mao Mingy
2015-01-26 10:55                         ` Stefano Stabellini
2015-01-23 10:33         ` Stefano Stabellini

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=54C21C86.5010006@gmail.com \
    --to=maomingya928@gmail.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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.