All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>,
	"Jan Beulich" <JBeulich@suse.com>
Cc: xen-devel@lists.xenproject.org, Tim Deegan <tim@xen.org>
Subject: Re: Removing the PVH assert in arch/x86/hvm/io.c:87
Date: Fri, 5 Dec 2014 11:24:26 +0000	[thread overview]
Message-ID: <548195EA.5050101@citrix.com> (raw)
In-Reply-To: <54819200.3010601@citrix.com>

On 05/12/14 11:07, Roger Pau Monné wrote:
> El 05/12/14 a les 10.15, Jan Beulich ha escrit:
>>>>> On 04.12.14 at 17:35, <roger.pau@citrix.com> wrote:
>>> I've just stumbled upon this assert while testing PVH on different
>>> hardware. It was added in 7c4870 as a safe belt, but it turns out INS
>>> and OUTS go through handle_mmio. So using this instructions from a PVH
>>> guest basically kills Xen.
>>>
>>> I've removed it and everything seems fine, so I'm considering sending a
>>> patch for 4.5 in order to have it removed. I think the path that could
>>> trigger the crash because of the missing vioapic stuff is already
>>> guarded by the other chunk added in the same patch.
>>
>> Iirc we settled on forbidding paths to handle_mmio() for PVH (hence
>> the ASSERT()). Sadly you provide way too little detail on what is
>> actually happening in your case: What's the use case of to-be-
>> emulated INS/OUTS in a PVH kernel?
> 
> In this specific situation I'm seeing intsw instructions executed by the
> FreeBSD ATA layer:
> 
> http://fxr.watson.org/fxr/source/dev/ata/ata-lowlevel.c#L740

Why are you running this device driver at all in a PVH guest?  It should
only be using PV block devices.

David

  reply	other threads:[~2014-12-05 11:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-04 16:35 Removing the PVH assert in arch/x86/hvm/io.c:87 Roger Pau Monné
2014-12-05  1:04 ` Mukesh Rathor
2014-12-05  9:15 ` Jan Beulich
2014-12-05 11:07   ` Roger Pau Monné
2014-12-05 11:24     ` David Vrabel [this message]
2014-12-05 11:26     ` Jan Beulich

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=548195EA.5050101@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=roger.pau@citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xenproject.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.