>>> On 16.11.16 at 17:49, wrote:
> On Fri, Nov 11, 2016 at 03:04:49AM -0700, Jan Beulich wrote:
>> >>> On 10.11.16 at 18:21, wrote:
>> > On Thu, Nov 10, 2016 at 04:20:34PM +0100, Roger Pau Monné wrote:
>> >> > 0a:11.4 Ethernet controller: Intel Corporation 82576 Virtual Function
>> >> > (rev 01)
>>> On 16.11.16 at 17:42, wrote:
> I assume that temporary limiting PVHv2 Dom0 support to systems with 1 IO APIC
> only is not going to be accepted, right?
Well, as long as it's experimental (and the respective code clearly
marked with fixme annotations) that would be acceptable imo.
Jan
On Fri, Nov 11, 2016 at 03:04:49AM -0700, Jan Beulich wrote:
> >>> On 10.11.16 at 18:21, wrote:
> > On Thu, Nov 10, 2016 at 04:20:34PM +0100, Roger Pau Monné wrote:
> >> > 0a:11.4 Ethernet controller: Intel Corporation 82576 Virtual Function
> >> > (rev 01)
> >> > Subsystem: Super Micro Co
On Thu, Nov 10, 2016 at 09:37:19AM -0700, Jan Beulich wrote:
> >>> On 10.11.16 at 11:39, wrote:
> > On Wed, Nov 09, 2016 at 01:45:17PM -0500, Konrad Rzeszutek Wilk wrote:
> >> On Wed, Nov 09, 2016 at 04:59:12PM +0100, Roger Pau Monné wrote:
> >> > PCI memory BARs
> >> > ---
> >> >
> >
>>> On 10.11.16 at 18:21, wrote:
> On Thu, Nov 10, 2016 at 04:20:34PM +0100, Roger Pau Monné wrote:
>> > 0a:11.4 Ethernet controller: Intel Corporation 82576 Virtual Function
>> > (rev 01)
>> > Subsystem: Super Micro Computer Inc Device 10c9
>> > Flags: bus master, fast devsel, lat
On Thu, Nov 10, 2016 at 04:20:34PM +0100, Roger Pau Monné wrote:
> On Thu, Nov 10, 2016 at 08:53:05AM -0500, Konrad Rzeszutek Wilk wrote:
> > On Thu, Nov 10, 2016 at 11:39:08AM +0100, Roger Pau Monné wrote:
> > > On Wed, Nov 09, 2016 at 01:45:17PM -0500, Konrad Rzeszutek Wilk wrote:
> > > > On Wed,
On Thu, Nov 10, 2016 at 09:37:19AM -0700, Jan Beulich wrote:
> >>> On 10.11.16 at 11:39, wrote:
> > On Wed, Nov 09, 2016 at 01:45:17PM -0500, Konrad Rzeszutek Wilk wrote:
> >> On Wed, Nov 09, 2016 at 04:59:12PM +0100, Roger Pau Monné wrote:
> >> > PCI memory BARs
> >> > ---
> >> >
> >
>>> On 10.11.16 at 11:39, wrote:
> On Wed, Nov 09, 2016 at 01:45:17PM -0500, Konrad Rzeszutek Wilk wrote:
>> On Wed, Nov 09, 2016 at 04:59:12PM +0100, Roger Pau Monné wrote:
>> > PCI memory BARs
>> > ---
>> >
>> > PCI devices discovered by Xen will have it's BARs scanned in order to
On Thu, Nov 10, 2016 at 08:53:05AM -0500, Konrad Rzeszutek Wilk wrote:
> On Thu, Nov 10, 2016 at 11:39:08AM +0100, Roger Pau Monné wrote:
> > On Wed, Nov 09, 2016 at 01:45:17PM -0500, Konrad Rzeszutek Wilk wrote:
> > > On Wed, Nov 09, 2016 at 04:59:12PM +0100, Roger Pau Monné wrote:
> > > > In orde
On Thu, Nov 10, 2016 at 11:39:08AM +0100, Roger Pau Monné wrote:
> On Wed, Nov 09, 2016 at 01:45:17PM -0500, Konrad Rzeszutek Wilk wrote:
> > On Wed, Nov 09, 2016 at 04:59:12PM +0100, Roger Pau Monné wrote:
> > > Hello,
> > >
> > > I'm attaching a draft of how a PVHv2 Dom0 is supposed to interact
On 10/11/16 10:54, Roger Pau Monné wrote:
> On Wed, Nov 09, 2016 at 06:51:49PM +, Andrew Cooper wrote:
>> On 09/11/16 15:59, Roger Pau Monné wrote:
>>> Low 1MB
>>> ---
>>>
>>> When booted with a legacy BIOS, the low 1MB contains firmware related data
>>> that should be identity mapped to th
On Wed, Nov 09, 2016 at 06:51:49PM +, Andrew Cooper wrote:
> On 09/11/16 15:59, Roger Pau Monné wrote:
> > Low 1MB
> > ---
> >
> > When booted with a legacy BIOS, the low 1MB contains firmware related data
> > that should be identity mapped to the Dom0. This include the EBDA, video
> > memo
On 09/11/16 20:47, Pasi Kärkkäinen wrote:
> On Wed, Nov 09, 2016 at 06:51:49PM +, Andrew Cooper wrote:
>>> Low 1MB
>>> ---
>>>
>>> When booted with a legacy BIOS, the low 1MB contains firmware related data
>>> that should be identity mapped to the Dom0. This include the EBDA, video
>>> memo
On Wed, Nov 09, 2016 at 01:45:17PM -0500, Konrad Rzeszutek Wilk wrote:
> On Wed, Nov 09, 2016 at 04:59:12PM +0100, Roger Pau Monné wrote:
> > Hello,
> >
> > I'm attaching a draft of how a PVHv2 Dom0 is supposed to interact with
> > physical devices, and what needs to be done inside of Xen in orde
On Wed, Nov 09, 2016 at 06:51:49PM +, Andrew Cooper wrote:
> >
> > Low 1MB
> > ---
> >
> > When booted with a legacy BIOS, the low 1MB contains firmware related data
> > that should be identity mapped to the Dom0. This include the EBDA, video
> > memory and possibly ROMs. All non RAM region
On 09/11/16 15:59, Roger Pau Monné wrote:
> Hello,
>
> I'm attaching a draft of how a PVHv2 Dom0 is supposed to interact with
> physical devices, and what needs to be done inside of Xen in order to
> achieve it. Current draft is RFC because I'm quite sure I'm missing bits
> that should be writte
On Wed, Nov 09, 2016 at 04:59:12PM +0100, Roger Pau Monné wrote:
> Hello,
>
> I'm attaching a draft of how a PVHv2 Dom0 is supposed to interact with
> physical devices, and what needs to be done inside of Xen in order to
> achieve it. Current draft is RFC because I'm quite sure I'm missing bits
Hello,
I'm attaching a draft of how a PVHv2 Dom0 is supposed to interact with
physical devices, and what needs to be done inside of Xen in order to
achieve it. Current draft is RFC because I'm quite sure I'm missing bits
that should be written down here. So far I've tried to describe what my
p
18 matches
Mail list logo