xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Vasiliy G Tolstov <v.tolstov@selfip.ru>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: use xs_watch from userspace and use epoll instead of select
Date: Mon, 06 Jun 2011 14:05:12 +0400	[thread overview]
Message-ID: <1307354712.28250.7.camel@vase> (raw)
In-Reply-To: <1307353709.775.431.camel@zakaz.uk.xensource.com>

On Mon, 2011-06-06 at 10:48 +0100, Ian Campbell wrote:
> On Mon, 2011-06-06 at 09:58 +0100, Vasiliy G Tolstov wrote:
> > Code to using from domU. I'm correct all my mistakes and now relative
> > and full path watches work's fine with epoll and select based looping.
> > Sorry for wrong panic about it. 
> 
> Oh good.
> 
> > Sorry for small offtop, where i can find example to use grand pages to
> > transfer for example 1byte from domU to dom) and vice versa?
> 
> (it's "grant" pages).
> 
> Any of the PV drivers would give a decent example for in kernel use of
> grant tables to setup a shared memory buffer, but I guess you are asking
> for a userspace example? The principals are mostly the same, except you
> use xc_* functions instead of the kernel ones.
> 
> qemu contains some userspace backends, for example the xenfb backend.
> Daniel de Graaf posted some patches to make this use grant tables back
> in February/March this year -- you should check the ML archives. There
> are also PV disk and net backends in qemu.
> 
> I can't think of any userspace frontends offhand.
> 
> Once you have a shared page you can use the standard Xen ring.h
> datastructures to define your request and response protocol.
> 
> What are you actually trying to build?
> 
> Ian.
> 

I'm try to build daemon, that can recieve command via xenstore (xs_watch
for specific path), via /dev/hvcN (serial char interface), now i'm try
to use gntmem mechanism to do this too. If one method not available or
not work or some errors accured - i'm try next. 
/dev/hvcN Not good sometimes, becouse in some domU i have gentty on this
port.
xenstore - has limit in size of message...
In kernel side xen thing more easy to understand. Use it under userspace
need deep googling =).
Ok if i use grant pages mechanism - do i have notify for new message
after it arrives? If i use xs from domU i need libxc under it insted of
libxenstore ?

-- 
Vasiliy G Tolstov <v.tolstov@selfip.ru>
Selfip.Ru

  reply	other threads:[~2011-06-06 10:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-03 12:04 use xs_watch from userspace and use epoll instead of select Vasiliy G Tolstov
2011-06-03 12:13 ` Ian Campbell
2011-06-03 12:17   ` Vasiliy G Tolstov
2011-06-03 16:07     ` Vasiliy G Tolstov
2011-06-06  8:41       ` Ian Campbell
2011-06-06  8:58         ` Vasiliy G Tolstov
2011-06-06  9:48           ` Ian Campbell
2011-06-06 10:05             ` Vasiliy G Tolstov [this message]
2011-06-06 11:00               ` Ian Campbell
2011-06-06 11:18                 ` Vasiliy G Tolstov
2011-06-06 11:26                   ` Ian Campbell

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=1307354712.28250.7.camel@vase \
    --to=v.tolstov@selfip.ru \
    --cc=Ian.Campbell@eu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).