From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: [RFC v2 0/5] HPET fix interrupt logic Date: Thu, 7 Nov 2013 15:28:20 +0000 Message-ID: <1383838105-9775-1-git-send-email-andrew.cooper3@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Xen-devel Cc: Andrew Cooper , Keir Fraser , Jan Beulich , Tim Deegan List-Id: xen-devel@lists.xenproject.org With the earlier patches now committed, this series is much shorter. I have split as many changes as I think I can unpick from the main functional change. These now live in patches 1 and 3. Some of the changes pulled forwards into patch 1 make a sup prising improvement to the clarity of patch 2. Patch 2 is the main functional change, which completely reimplements how HPET interrupts work, how ownership works, and how waking works. It is RFC, and is currently tested as "Doesn't blow up when used". This includes more modern systems as well, using the "no-arat" command line parameter to cause Xen to use this codepath. Patches 4 and 5 are debugging, and possibly for inclusion if deemed useful. Signed-off-by: Andrew Cooper CC: Keir Fraser CC: Jan Beulich CC: Tim Deegan -- 1.7.10.4