All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "edk2-devel@ml01.01.org" <edk2-devel@ml01.01.org>,
	"KVM devel mailing list" <kvm@vger.kernel.org>,
	"Radim Krčmář" <rkrcmar@redhat.com>
Subject: Re: [edk2] apparent SMBASE relocation issue with noexec enabled [was: MdeModulePkg DxeIpl: Add stack NX support]
Date: Fri, 7 Aug 2015 00:38:25 +0200	[thread overview]
Message-ID: <55C3E1E1.70504@redhat.com> (raw)
In-Reply-To: <55C3755D.4000408@redhat.com>

On 08/06/15 16:55, Paolo Bonzini wrote:
> 
> 
> On 06/08/2015 16:31, Laszlo Ersek wrote:
>>> kvm_cpuid:            func 80000001 rax 6e8 rbx 0 rcx 0 rdx 100000
>>> kvm_enter_smm:        vcpu 0: leaving SMM, smbase 0x7ffc0000
>>> kvm_entry:            vcpu 0
>>> kvm_exit:             reason TRIPLE_FAULT rip 0x7ffdb6b2 info 0 0
>>> kvm_userspace_exit:   reason KVM_EXIT_SHUTDOWN (8)
> 
> Can you provide a trace with both kvm and kvmmmu events enabled?

The "trace-cmd report" command printed the following to stderr:

trace-cmd: No such file or directory
  function is_writable_pte not defined

Not sure how serious that is; FWIW it did produce a human readable
report. Please find it at
<http://people.redhat.com/~lersek/smbase_reloc_triple_fault/trace.txt.xz>.

The trace covers the full lifetime of the guest (I started tracing
before launching the guest, and I passed -no-reboot to qemu, so when the
guest crashed, QEMU exited.)

This was on 3.10.0-299.el7.x86_64.

Thank you!
Laszlo

  reply	other threads:[~2015-08-06 22:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1438345360-7076-1-git-send-email-star.zeng@intel.com>
     [not found] ` <55C22EC0.2030400@redhat.com>
     [not found]   ` <43260721-AB29-4182-8961-D33A70C5377B@apple.com>
     [not found]     ` <55C23994.4000804@redhat.com>
     [not found]       ` <0C09AFA07DD0434D9E2A0C6AEB04831002175554@shsmsx102.ccr.corp.intel.com>
     [not found]         ` <55C31D59.6060400@redhat.com>
     [not found]           ` <0C09AFA07DD0434D9E2A0C6AEB04831002175A03@shsmsx102.ccr.corp.intel.com>
     [not found]             ` <55C36446.1030904@redhat.com>
2015-08-06 14:31               ` [edk2] apparent SMBASE relocation issue with noexec enabled [was: MdeModulePkg DxeIpl: Add stack NX support] Laszlo Ersek
2015-08-06 14:55                 ` Paolo Bonzini
2015-08-06 22:38                   ` Laszlo Ersek [this message]
2015-08-06 23:02                     ` Laszlo Ersek
2015-08-07 10:38                       ` Paolo Bonzini
2015-08-07 13:12                         ` Laszlo Ersek

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=55C3E1E1.70504@redhat.com \
    --to=lersek@redhat.com \
    --cc=edk2-devel@ml01.01.org \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@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.