[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FW: [Xen-introspect] Status Update


  • To: xen-introspect@xxxxxxxxxxxxxxxxxxx
  • From: "Bryan D. Payne" <bryan@xxxxxxxxxxxx>
  • Date: Mon, 8 Jun 2009 15:59:21 -0400
  • Delivery-date: Mon, 08 Jun 2009 12:59:27 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=KkNzRuiehUgnvTTGjAaqoyaAJ06bAYzV+2DQiVxQmX96MmTU0fyx3tJIWgNUZYKm+k GAw95T2J2zkhfRjlh7PuzK8cP2mOPIF4MayUOunN6VLPTLLbj1UdIQVuB7U8SXisENrg EnK0Twha/FB5PHqoAUKFAvdUclaVUUhPTmpFg=
  • List-id: xen-introspect.lists.xensource.com

> Personally I'd like to see it upstream and promoted as a core API. I think we 
> just need to get a bit of momentum behind this and then it will snowball and 
> folks like security vendors will get involved.

I'd be happy to work in this direction.  What would be the best way to
proceed with something like this?  Should we ultimately provide a
patch to xen-devel?  If so, how stable (with regard to features...
code stability seems to be quite good right now from my experiences)
should XenAccess be before we take that step?  Are there particular
features and/or coding standards that we would need to provide to
integrate more cleanly with Xen?

Cheers,
bryan


-- 
Bryan D. Payne
Research Scientist & Graduate Student
Georgia Tech Information Security Center
http://www.bryanpayne.org

_______________________________________________
Xen-introspect mailing list
Xen-introspect@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-introspect


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.