This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


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.


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.
Xen-devel mailing list