All of lore.kernel.org
 help / color / mirror / Atom feed
From: Prarit Bhargava <prarit@redhat.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: linux-kernel@vger.kernel.org, suresh.b.siddha@intel.com,
	x86@kernel.org, clalance@redhat.com, drjones@redhat.com
Subject: Re: [LKML] Re: [LKML] [PATCH] Fix NULL pointer for Xen guests
Date: Tue, 04 May 2010 11:21:55 -0400	[thread overview]
Message-ID: <4BE03B93.1010005@redhat.com> (raw)
In-Reply-To: <20100504150214.GA5667@phenom.dumpdata.com>


> Interestingly enough, I couldn't reproduce this on my Intel box, but on
> a AMD box with a very wacked TSC (cpu MHz         : 2795681.405) I can
> reproduce this.
>
>    

Huh ... that's odd.  I'll grab a dinar based system and see if I can 
reproduce it there.  It would be interesting to know what the 
differences are.

P.

  reply	other threads:[~2010-05-04 15:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-27 15:24 [PATCH] Fix NULL pointer for Xen guests Prarit Bhargava
2010-04-27 16:58 ` [LKML] " Konrad Rzeszutek Wilk
2010-04-27 17:09   ` Prarit Bhargava
2010-04-27 17:59     ` Andrew Jones
2010-04-27 18:34     ` Konrad Rzeszutek Wilk
2010-04-27 18:47       ` Prarit Bhargava
2010-05-03 19:16         ` Konrad Rzeszutek Wilk
2010-05-03 19:56           ` Prarit Bhargava
2010-05-04 15:02           ` [LKML] " Konrad Rzeszutek Wilk
2010-05-04 15:21             ` Prarit Bhargava [this message]
2010-04-28 18:26 ` Andrew Morton
2010-04-28 18:29   ` Prarit Bhargava
2010-04-28 18:42     ` Suresh Siddha
2010-04-28 18:50     ` Andrew Morton
2010-04-28 19:15       ` [stable] " Greg KH
2010-04-30 20:55 ` H. Peter Anvin
2010-04-30 21:33   ` H. Peter Anvin
2010-04-30 22:01   ` Prarit Bhargava
2010-04-30 21:36 ` [tip:x86/urgent] x86: Fix NULL pointer access in irq_force_complete_move() " tip-bot for Prarit Bhargava
2010-05-04 15:02   ` [LKML] " Konrad Rzeszutek Wilk

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=4BE03B93.1010005@redhat.com \
    --to=prarit@redhat.com \
    --cc=clalance@redhat.com \
    --cc=drjones@redhat.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suresh.b.siddha@intel.com \
    --cc=x86@kernel.org \
    /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.