| |
|
 |
|
 |
|
|
|
| |
|
|
xen-introspect
RE: FW: [Xen-introspect] Status Update
> > 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?
Posting to xen-devel soner rather than later is definitely worthwhile to get
some more exposure and feedback. It would be great if that could then prompt
some factoring of common code with Mukesh's debugger.
Thanks,
Ian
_______________________________________________
Xen-introspect mailing list
Xen-introspect@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-introspect
|
|
|
| |
|
Home