Re: [Xen-devel] Blocking upcall to dom0

Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:
> >That's what I was originally thinking, but from Keir's first reply it
> >seems that I can't arbitrarily block within Xen since stacks are 
> >per-CPU rather than per-domain.
> >
> >I'd like to block within Xen and resume at that same point in Xen, not
> >in the guest.  If I understand the flow of things correctly, then using
> >an event channel and blocking will resume the domain from the guest's
> >last execution context, rather than Xen's.  Please correct me if I'm
> >wrong.
> 
> Yes that's right. So you want to block on communications that the guest 
> is unaware of?

Yes, exactly.  I'm looking at ways to do intrusion detection on the
guest kernel, so I want to decide whether the guest should continue
without it being involved in the decision or information flow.

Andrew


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread]

Current Thread

[Next in Thread>

Previous by Date:

Re: Re: Re: [Xen-devel] Proposal for init/kexec/hotplug format for Xen, Harry Butterworth

Next by Date:

RE: [Xen-devel] AGP & Binary Nvidia Drivers, Ian Pratt

Previous by Thread:

Re: [Xen-devel] Blocking upcall to dom0, Keir Fraser

Next by Thread:

Re: [Xen-devel] Blocking upcall to dom0, Keir Fraser

Indexes:

[Date] [Thread] [Top] [All Lists]