All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roedel, Joerg" <Joerg.Roedel@amd.com>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	Gleb Natapov <gleb@redhat.com>
Subject: Re: [PATCH 1/1] KVM: Pull extra page fault information into struct x86_exception
Date: Mon, 29 Nov 2010 17:25:58 +0100	[thread overview]
Message-ID: <20101129162558.GE2258@amd.com> (raw)
In-Reply-To: <1291039950-8418-2-git-send-email-avi@redhat.com>

On Mon, Nov 29, 2010 at 09:12:30AM -0500, Avi Kivity wrote:
> Currently page fault cr2 and nesting infomation are carried outside
> the fault data structure.  Instead they are placed in the vcpu struct,
> which results in confusion as global variables are manipulated instead
> of passing parameters.
> 
> Fix this issue by adding address and nested fields to struct x86_exception,
> so this struct can carry all information associated with a fault.

Tested with nnpt and found no regressions.

> Signed-off-by: Avi Kivity <avi@redhat.com>

Tested-by: Joerg Roedel <joerg.roedel@amd.com>

-- 
AMD Operating System Research Center

Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632


  reply	other threads:[~2010-11-29 16:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-29 14:12 [PATCH 0/1] Clean up page fault injection Avi Kivity
2010-11-29 14:12 ` [PATCH 1/1] KVM: Pull extra page fault information into struct x86_exception Avi Kivity
2010-11-29 16:25   ` Roedel, Joerg [this message]
2010-11-30 11:20   ` Gleb Natapov
2010-11-29 15:40 ` [PATCH 0/1] Clean up page fault injection Roedel, Joerg
2010-12-02  2:07 ` Marcelo Tosatti

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=20101129162558.GE2258@amd.com \
    --to=joerg.roedel@amd.com \
    --cc=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.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.