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

Re: [Xen-devel] Question to console input events


  • To: Keir Fraser <keir@xxxxxxxxxxxxx>
  • From: Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxxxxxxx>
  • Date: Thu, 11 Jan 2007 14:45:46 +0100
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 11 Jan 2007 05:45:21 -0800
  • Domainkey-signature: s=s768; d=fujitsu-siemens.com; c=nofws; q=dns; b=b+Tf2cCg0vWelD98HysPE/Nb5PJXTX4+ldegqPGPjo8scZqcJUydjAvZmf2+9qtusbLc54bpB23iguS379QMfzVFy/zDb897oU2ZRRQ+jUiBASRA46zm92Zr3njesTT3;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Am Donnerstag, 11. Januar 2007 09:32 schrieb Keir Fraser:
> On 11/1/07 8:04 am, "Dietmar Hahn" <dietmar.hahn@xxxxxxxxxxxxxxxxxxx> wrote:
> > I try to port the mini-os to ia64 and have a problem with using
> > hypervisor call:
> > HYPERVISOR_sched_op(SCHEDOP_block, 0);
> > to block the domU.
> > The problem is, that the domU never (or a very short time) gets blocked
> > because the domU gets lots of console events. But all the time no data
> > are in the console input buffer.
> > Can anybody explain where and when the console events are generated
> > therewidth I can have a look in the source.
>
> The other end of the event channel is held by the console daemon. Its code
> is in tools/console/daemon. Look for its uses of xc_evtchn_notify().
>
>  -- Keir

Hi Keir,

many thanks for your hint! Now I understand the concept and my problem.
Thanks.

Dietmar.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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