All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <nsnix@comcast.net>
To: Harry Butterworth <harry@hebutterworth.freeserve.co.uk>
Cc: xen-devel@lists.xensource.com,
	Mark Williamson <mark.williamson@cl.cam.ac.uk>
Subject: Re: Re: USB virt status
Date: Fri, 04 Nov 2005 20:08:09 -0800	[thread overview]
Message-ID: <436C3029.5040902@comcast.net> (raw)
In-Reply-To: <1131157306.4740.65.camel@localhost>

Harry Butterworth wrote:
> On Sat, 2005-11-05 at 00:50 +0000, Mark Williamson wrote:

>>Yes, right now I'm working with Xenstore too.  The updates I mentioned are 
>>supposed to tackle this problem by providing a better API, automating the 
>>channel setup state machine for the majority of users (i.e. all devices).  I 
>>believe a some of this code is fully completed and awaiting push to the main 
>>tree once it's been reviewed by a few people.

Hi Mark,

I didn't see the original email that Harry quoted, but could
you elaborate on that? Are you proposing a new API? Why only
a few people? Any reason not on the list?

Rusty had asked a question regarding what's in 3.0:
http://marc.theaimsgroup.com/?l=xen-devel&m=113038760216447&w=2

and I guess I'll second that..


>>I really would have liked to see a more abstract interface to communications, 
>>such as the one you propose.  However, it is not going to happen for the 3.0 
>>release and that's when the team promised the interfaces will be frozen.  If 
>>it can't be compatible with the existing interfaces, that's going to make it 
>>much less likely that anyone will update the existing drivers and then 
>>maintain two separate interdomain interfaces for each.
>>
>>I think the project is likely to follow the path of least resistance and go 
>>with a "xenstore connection setup library" that replaces most of the 
>>duplicate code but retain the old datapath API.  I get the impression this 
>>decision has been taken already.

Any reason for this to not be shared on xen-devel?

thanks,
Nivedita

  reply	other threads:[~2005-11-05  4:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-30 16:43 USB virt status Harry Butterworth
     [not found] ` <200511041725.11451.mark.williamson@cl.cam.ac.uk>
     [not found]   ` <1131130680.3019.87.camel@localhost.localdomain>
     [not found]     ` <200511050050.58120.mark.williamson@cl.cam.ac.uk>
2005-11-05  2:21       ` Harry Butterworth
2005-11-05  4:08         ` Nivedita Singhvi [this message]
2005-11-05 10:32           ` Keir Fraser
2005-11-05 11:30             ` Harry Butterworth
2005-11-05 18:00             ` Nivedita Singhvi
2005-11-05 13:06           ` Mark Williamson
2005-11-05 12:32         ` Mark Williamson

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=436C3029.5040902@comcast.net \
    --to=nsnix@comcast.net \
    --cc=harry@hebutterworth.freeserve.co.uk \
    --cc=mark.williamson@cl.cam.ac.uk \
    --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.