xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: ravi kerur <rkerur@gmail.com>
To: Daniel Stodden <daniel.stodden@citrix.com>
Cc: Paul Durrant <Paul.Durrant@citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Q on ioctl support in netfront/netback
Date: Wed, 17 Feb 2010 07:44:02 -0800	[thread overview]
Message-ID: <dfc283f41002170744x7540ae4bp84c5ae07b0a425de@mail.gmail.com> (raw)
In-Reply-To: <1266377170.15135.13710.camel@agari.van.xensource.com>


[-- Attachment #1.1: Type: text/plain, Size: 1591 bytes --]

Hi Daniel,

These registers are(DMA, statistics, and other h/w related to NIC), I just
want to read those registers and in very few cases write to them. Currently,
I can run those applications in dom0 and access directly but I wanted to
check if anything is possible from domU? Other thing I tried using sockets
from domU to dom0(albeit I had clear firewall settings in dom0) but Citrix
support forum mentioned it is not the recommended way. I am not sure whether
I answered your question, let me know if you need additional info.

Thanks
-RK

On Tue, Feb 16, 2010 at 7:26 PM, Daniel Stodden
<daniel.stodden@citrix.com>wrote:

> On Mon, 2010-02-15 at 10:54 -0500, ravi kerur wrote:
> > Paul,
> >
> > Registers are not in netback, they are h/w registers on NIC and the
> > driver supports reads/writes via ioctl calls. Driver is in dom0 and
> > application which reads/writes registers is run in domU.
>
> Why do you want to map or preserve some register interface?
>
> Is this some sort of hardware multiplex? As Konrad pointed out, in that
> case a PV driver is probably the wrong approach altogether.
>
> If what you want is just a bunch of extended control plane attributes,
> rather consider mapping them to xenstore.
>
> That's slightly more asynchronous and probably not a great option if you
> need a synchronous interface. Especially if you need individual return
> values, not just a bunch of fields to write into.
>
> If the latter case, next option would be some dedicated shared memory
> structure. But it's hard to imagine something like that to make
> sense. :}
>
> Daniel
>
>

[-- Attachment #1.2: Type: text/html, Size: 2065 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

      reply	other threads:[~2010-02-17 15:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-15  2:23 Q on ioctl support in netfront/netback ravi kerur
2010-02-15  9:40 ` Paul Durrant
2010-02-15 15:54   ` ravi kerur
2010-02-16 18:14     ` Konrad Rzeszutek Wilk
2010-02-17 16:19       ` ravi kerur
2010-02-17 16:27         ` Pasi Kärkkäinen
2010-02-17 16:40         ` Konrad Rzeszutek Wilk
2010-02-17 20:00           ` ravi kerur
2010-02-17  3:26     ` Daniel Stodden
2010-02-17 15:44       ` ravi kerur [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=dfc283f41002170744x7540ae4bp84c5ae07b0a425de@mail.gmail.com \
    --to=rkerur@gmail.com \
    --cc=Paul.Durrant@citrix.com \
    --cc=daniel.stodden@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).