All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	keir@xen.org, xen-devel@lists.xen.org
Subject: Re: [PATCH v2 0/2] Support of RO MMCFG access for PVH/HVMlite dom0s
Date: Fri, 18 Dec 2015 07:16:53 -0700	[thread overview]
Message-ID: <5674236502000078000C143B@prv-mh.provo.novell.com> (raw)
In-Reply-To: <56740FE7.60301@oracle.com>

>>> On 18.12.15 at 14:53, <boris.ostrovsky@oracle.com> wrote:
> On 12/18/2015 08:02 AM, Andrew Cooper wrote:
>> On 18/12/15 10:11, Jan Beulich wrote:
>>>>>> On 17.12.15 at 21:22, <boris.ostrovsky@oracle.com> wrote:
>>>> * Left non-MMCFG RO accesses unhandled (we havent't encountered those 
> accesses
>>>>    yet with PVH dom0 and it's probably better to fault on them and 
> investigate
>>>>    whether they are guest's issues).
>>> I seriously question this being a good approach,
>> I concur.  All accesses should be terminated somehow, even if this is
>> the hypervisor dropping writes and completing reads with ~0's.
>>
>> This is the expected behaviour from the x86 architecture.
> 
> OK, I'll add that in.
> 
> To answer Jan's question, I did try 'vga=keep' and that worked fine.

Interesting. Does your system not load/use a DRM driver for the
card? Or is the driver so minimalistic that no extended config
space write ever occurs?

Jan

  reply	other threads:[~2015-12-18 14:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 20:22 [PATCH v2 0/2] Support of RO MMCFG access for PVH/HVMlite dom0s Boris Ostrovsky
2015-12-17 20:22 ` [PATCH v2 1/2] x86/mm: Add information about faulted page's presence to npfec structure Boris Ostrovsky
2015-12-18 10:15   ` Jan Beulich
2015-12-20  6:49     ` Tian, Kevin
2015-12-17 20:22 ` [PATCH v2 2/2] x86/PCI: Intercept Dom0 MMCFG from dom0s in HVM containers Boris Ostrovsky
2015-12-18 10:28   ` Jan Beulich
2015-12-18 10:11 ` [PATCH v2 0/2] Support of RO MMCFG access for PVH/HVMlite dom0s Jan Beulich
2015-12-18 13:02   ` Andrew Cooper
2015-12-18 13:53     ` Boris Ostrovsky
2015-12-18 14:16       ` Jan Beulich [this message]
2015-12-18 14:30         ` Boris Ostrovsky
2015-12-18 14:36           ` 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=5674236502000078000C143B@prv-mh.provo.novell.com \
    --to=jbeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=keir@xen.org \
    --cc=xen-devel@lists.xen.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.