From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>, keir.xen@gmail.com
Subject: Re: [RFC 0 PATCH 3/3] PVH dom0: construct_dom0 changes
Date: Fri, 4 Oct 2013 16:59:53 -0400 [thread overview]
Message-ID: <20131004205953.GA22446@phenom.dumpdata.com> (raw)
In-Reply-To: <524F03FF02000078000F8F4A@nat28.tlf.novell.com>
On Fri, Oct 04, 2013 at 05:07:59PM +0100, Jan Beulich wrote:
> >>> On 04.10.13 at 18:02, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> > So back to hooking up a new hypercall in the PCI subsystem when
> > resource assigment has been completed? And also if the PCI subsystem
> > decides to re-write the resource addresses to odd locations.
> >
> > Can't one also trap for the configuration changes on the PCI
> > devices and extract the physical locations then?
>
> Yes, of course we could be snooping the CFG writes, but that's
> as simple as it sounds only for the port CF8 based accesses. For
> MCFG based accesses it would mean we'd have to write protect
> the whole MCFG range, and use emulation there. Not very
> pretty, but doable.
Hypervisor call is then a more appropiate if it can be done (Mukesh
says that v0 of the patch had something like that in so he will try
to recreate it) and then as a fallback we could do the emulation.
>
> Jan
>
next prev parent reply other threads:[~2013-10-04 21:00 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 21:03 [RFC 0 PATCH 0/3]: PVH dom0 construction Mukesh Rathor
2013-09-25 21:03 ` [RFC 0 PATCH 1/3] PVH dom0: create domctl_memory_mapping() function Mukesh Rathor
2013-09-26 7:03 ` Jan Beulich
2013-09-25 21:03 ` [RFC 0 PATCH 2/3] PVH dom0: move some pv specific code to static functions Mukesh Rathor
2013-09-26 7:21 ` Jan Beulich
2013-09-26 23:32 ` Mukesh Rathor
2013-09-25 21:03 ` [RFC 0 PATCH 3/3] PVH dom0: construct_dom0 changes Mukesh Rathor
2013-09-26 8:02 ` Jan Beulich
2013-09-27 0:17 ` Mukesh Rathor
2013-09-27 6:54 ` Jan Beulich
2013-10-03 0:53 ` Mukesh Rathor
2013-10-04 6:53 ` Jan Beulich
2013-10-04 13:35 ` Konrad Rzeszutek Wilk
2013-10-04 14:05 ` Jan Beulich
2013-10-04 16:02 ` Konrad Rzeszutek Wilk
2013-10-04 16:07 ` Jan Beulich
2013-10-04 20:59 ` Konrad Rzeszutek Wilk [this message]
2013-10-05 1:06 ` Mukesh Rathor
2013-10-07 7:12 ` Jan Beulich
2013-10-08 0:58 ` Mukesh Rathor
2013-10-08 7:51 ` Jan Beulich
2013-10-08 8:03 ` Jan Beulich
2013-10-08 9:39 ` George Dunlap
2013-10-08 9:57 ` Jan Beulich
2013-10-08 10:01 ` George Dunlap
2013-10-08 10:19 ` Lars Kurth
2013-10-08 12:30 ` Konrad Rzeszutek Wilk
2013-10-09 13:02 ` George Dunlap
2013-10-09 13:13 ` Andrew Cooper
2013-10-09 13:16 ` George Dunlap
2013-10-09 14:37 ` Andrew Cooper
2013-10-09 17:50 ` Tim Deegan
2013-10-09 22:31 ` Mukesh Rathor
2013-09-27 1:55 ` Mukesh Rathor
2013-09-27 7:01 ` Jan Beulich
2013-09-27 23:03 ` Mukesh Rathor
2013-09-30 6:56 ` Jan Beulich
2013-10-08 0:52 ` Mukesh Rathor
2013-10-08 7:43 ` Jan Beulich
2013-10-09 21:59 ` Mukesh Rathor
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=20131004205953.GA22446@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=keir.xen@gmail.com \
--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.