All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: xen-devel@lists.xensource.com
Cc: Gang Wei <gang.wei@intel.com>, ke.yu@intel.com
Subject: please revert c/s 17686
Date: Thu, 12 Jun 2008 14:28:49 +0100	[thread overview]
Message-ID: <485140B1.76E4.0078.0@novell.com> (raw)

Switching HPET into legacy mode is not acceptable, as this doesn't only
cut off the PIT channel 0 interrupt, but also the RTC one. The former is
acceptable as no domain will ever gain control over it, but the latter isn't
as Dom0 may validly make use of it. I'm observing a failure of setting the
system clock correctly due to this issue (hwclock checks whether the RTC
update interrupt is occurring as expected), and I suppose other uses of
/dev/rtc would also suffer.

It is my understanding that using the HPET to overcome the APIC timer
stop issue is therefore impossible at present - you cannot use legacy
mode, and you also cannot use the individual routing mode as whatever
IRQ is chosen may turn out being in use by one or more other devices
(and hence would require sharing the IRQ between Xen and one or more
guests).

Thanks, Jan

             reply	other threads:[~2008-06-12 13:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-12 13:28 Jan Beulich [this message]
2008-06-12 13:56 ` please revert c/s 17686 Keir Fraser
2008-06-12 14:01   ` Jan Beulich
2008-06-12 16:22 ` Keir Fraser
2008-06-13  2:08   ` Wei, Gang
2008-06-13  7:31     ` Keir Fraser
2008-06-13  7:45       ` Jan Beulich
2008-06-13  7:51         ` Keir Fraser
2008-06-13  8:06           ` Wei, Gang
2008-06-13  8:12             ` Jan Beulich
2008-06-13  8:24               ` Keir Fraser
2008-06-13 13:12                 ` Wei, Gang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=485140B1.76E4.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=gang.wei@intel.com \
    --cc=ke.yu@intel.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.