On 11/02/2017 01:34 PM, George Dunlap wrote:
> On 10/27/2017 04:09 PM, NathanStuder wrote:
>>
>>
>> On 10/09/2017 10:14 AM, Lars Kurth wrote:
>>>
On 27 Sep 2017, at 13:57, Robert VanVossen
wrote:
On 9/26/2017 3:12 AM, Dario Faggioli wrote:
> [Cc-list modified b
On 10/27/2017 04:09 PM, NathanStuder wrote:
>
>
> On 10/09/2017 10:14 AM, Lars Kurth wrote:
>>
>>> On 27 Sep 2017, at 13:57, Robert VanVossen
>>> wrote:
>>>
>>>
>>>
>>> On 9/26/2017 3:12 AM, Dario Faggioli wrote:
[Cc-list modified by removing someone and adding someone else]
On M
On Thu, Nov 02, 2017 at 10:46:20AM +, George Dunlap wrote:
> On 11/01/2017 05:10 PM, Konrad Rzeszutek Wilk wrote:
> > On Tue, Oct 24, 2017 at 04:22:38PM +0100, George Dunlap wrote:
> >> On Fri, Sep 15, 2017 at 3:51 PM, Konrad Rzeszutek Wilk
> >> wrote:
> +### Soft-reset for PV guests
> >>
On 11/01/2017 05:10 PM, Konrad Rzeszutek Wilk wrote:
> On Tue, Oct 24, 2017 at 04:22:38PM +0100, George Dunlap wrote:
>> On Fri, Sep 15, 2017 at 3:51 PM, Konrad Rzeszutek Wilk
>> wrote:
+### Soft-reset for PV guests
>>>
>>> s/PV/HVM/
>>
>> Is it? I thought this was for RHEL 5 PV guests to be
On Tue, Oct 24, 2017 at 04:22:38PM +0100, George Dunlap wrote:
> On Fri, Sep 15, 2017 at 3:51 PM, Konrad Rzeszutek Wilk
> wrote:
> >> +### Soft-reset for PV guests
> >
> > s/PV/HVM/
>
> Is it? I thought this was for RHEL 5 PV guests to be able to do crash
> kernels.
>
> >> +### Transcendent Me
On 09/12/2017 08:52 PM, Stefano Stabellini wrote:
>>> +### Xen Framebuffer
>>> +
>>> +Status, Linux: Supported
>>
>> Frontend?
>
> Yes, please. If you write "Xen Framebuffer" I only take it to mean the
> protocol as should be documented somewhere under docs/. Then I read
> Linux, and I don't u
On 09/12/2017 11:39 AM, Roger Pau Monné wrote:
> On Mon, Sep 11, 2017 at 06:01:59PM +0100, George Dunlap wrote:
>> +## Toolstack
>> +
>> +### xl
>> +
>> +Status: Supported
>> +
>> +### Direct-boot kernel image format
>> +
>> +Supported, x86: bzImage
>
> ELF
>
>> +Supported, ARM32: zIm
On 10/09/2017 10:14 AM, Lars Kurth wrote:
>
>> On 27 Sep 2017, at 13:57, Robert VanVossen
>> wrote:
>>
>>
>>
>> On 9/26/2017 3:12 AM, Dario Faggioli wrote:
>>> [Cc-list modified by removing someone and adding someone else]
>>>
>>> On Mon, 2017-09-25 at 16:10 -0700, Stefano Stabellini wrote:
>>
On 26/10/17 10:19, Jan Beulich wrote:
On 25.10.17 at 13:30, wrote:
>> On 25/10/17 11:59, George Dunlap wrote:
> +Limit, x86 HVM: 128
> +Limit, ARM32: 8
> +Limit, ARM64: 128
> +
> +[XXX Andrew Cooper: Do want to add "Limit-Security" here for
>>> On 25.10.17 at 13:30, wrote:
> On 25/10/17 11:59, George Dunlap wrote:
+Limit, x86 HVM: 128
+Limit, ARM32: 8
+Limit, ARM64: 128
+
+[XXX Andrew Cooper: Do want to add "Limit-Security" here for some of
these?]
>>> 32 for each
On 25/10/17 11:59, George Dunlap wrote:
>>> +Limit, x86 HVM: 128
>>> +Limit, ARM32: 8
>>> +Limit, ARM64: 128
>>> +
>>> +[XXX Andrew Cooper: Do want to add "Limit-Security" here for some of
>>> these?]
>> 32 for each. 64 vcpu HVM guests can excerpt enough p2
On Tue, Oct 24, 2017 at 12:42 PM, Andrew Cooper
wrote:
> On 24/10/17 11:27, George Dunlap wrote:
>> On 10/23/2017 06:55 PM, Andrew Cooper wrote:
>>> On 23/10/17 17:22, George Dunlap wrote:
On 09/11/2017 06:53 PM, Andrew Cooper wrote:
> On 11/09/17 18:01, George Dunlap wrote:
>> +### x
On Fri, Sep 15, 2017 at 3:51 PM, Konrad Rzeszutek Wilk
wrote:
>> +### Soft-reset for PV guests
>
> s/PV/HVM/
Is it? I thought this was for RHEL 5 PV guests to be able to do crash kernels.
>> +### Transcendent Memory
>> +
>> +Status: Experimental
>> +
>> +[XXX Add description]
>
> Guests wit
On Tue, Sep 12, 2017 at 4:35 PM, Rich Persaud wrote:
>> On Sep 11, 2017, at 13:01, George Dunlap wrote:
>>
>> +### XSM & FLASK
>> +
>> +Status: Experimental
>> +
>> +Compile time disabled
>> +
>> +### XSM & FLASK support for IS_PRIV
>> +
>> +Status: Experimental
>
> In which specific area
On 24/10/17 11:27, George Dunlap wrote:
> On 10/23/2017 06:55 PM, Andrew Cooper wrote:
>> On 23/10/17 17:22, George Dunlap wrote:
>>> On 09/11/2017 06:53 PM, Andrew Cooper wrote:
On 11/09/17 18:01, George Dunlap wrote:
> +### x86/RAM
> +
> +Limit, x86: 16TiB
> +Limit, A
Hi,
On 23/10/2017 18:55, Andrew Cooper wrote:
On 23/10/17 17:22, George Dunlap wrote:
On 09/11/2017 06:53 PM, Andrew Cooper wrote:
On 11/09/17 18:01, George Dunlap wrote:
+Limit, x86 HVM: 128
+Limit, ARM32: 8
+Limit, ARM64: 128
+
+[XXX Andrew Cooper: Do want to add "Limit-Security
On 10/23/2017 06:55 PM, Andrew Cooper wrote:
> On 23/10/17 17:22, George Dunlap wrote:
>> On 09/11/2017 06:53 PM, Andrew Cooper wrote:
>>> On 11/09/17 18:01, George Dunlap wrote:
+### x86/RAM
+
+Limit, x86: 16TiB
+Limit, ARM32: 16GiB
+Limit, ARM64: 5TiB
+
>
On Mon, 23 Oct 2017, Andrew Cooper wrote:
> >>> +### x86 PV/Event Channels
> >>> +
> >>> +Limit: 131072
> >> Why do we call out event channel limits but not grant table limits?
> >> Also, why is this x86? The 2l and fifo ABIs are arch agnostic, as far
> >> as I am aware.
> > Sure, but I'm pre
On 23/10/17 17:22, George Dunlap wrote:
> On 09/11/2017 06:53 PM, Andrew Cooper wrote:
>> On 11/09/17 18:01, George Dunlap wrote:
>>> +### x86/RAM
>>> +
>>> +Limit, x86: 16TiB
>>> +Limit, ARM32: 16GiB
>>> +Limit, ARM64: 5TiB
>>> +
>>> +[XXX: Andy to suggest what this should say for x86]
On 09/11/2017 06:53 PM, Andrew Cooper wrote:
> On 11/09/17 18:01, George Dunlap wrote:
>> +### x86/PV
>> +
>> +Status: Supported
>> +
>> +Traditional Xen Project PV guest
>
> What's a "Xen Project" PV guest? Just Xen here.
>
> Also, a perhaps a statement of "No hardware requirements" ?
OK.
> On 27 Sep 2017, at 13:57, Robert VanVossen
> wrote:
>
>
>
> On 9/26/2017 3:12 AM, Dario Faggioli wrote:
>> [Cc-list modified by removing someone and adding someone else]
>>
>> On Mon, 2017-09-25 at 16:10 -0700, Stefano Stabellini wrote:
>>> On Mon, 11 Sep 2017, George Dunlap wrote:
+#
> On 12 Sep 2017, at 16:35, Rich Persaud wrote:
>
>> On Sep 11, 2017, at 13:01, George Dunlap wrote:
>>
>> +### XSM & FLASK
>> +
>> +Status: Experimental
>> +
>> +Compile time disabled
>> +
>> +### XSM & FLASK support for IS_PRIV
>> +
>> +Status: Experimental
>
> In which specific are
On 9/26/2017 3:12 AM, Dario Faggioli wrote:
> [Cc-list modified by removing someone and adding someone else]
>
> On Mon, 2017-09-25 at 16:10 -0700, Stefano Stabellini wrote:
>> On Mon, 11 Sep 2017, George Dunlap wrote:
>>> +### RTDS based Scheduler
>>> +
>>> +Status: Experimental
>>> +
>>> +
On Wed, 2017-09-27 at 08:57 -0400, Robert VanVossen wrote:
> On 9/26/2017 3:12 AM, Dario Faggioli wrote:
> > [Cc-list modified by removing someone and adding someone else]
> >
> > Actually, the best candidate for gaining security support, is IMO
> > ARINC. Code is also rather simple and "stable" (
On 09/26/2017 12:10 AM, Stefano Stabellini wrote:
> On Mon, 11 Sep 2017, George Dunlap wrote:
>> +### RTDS based Scheduler
>> +
>> +Status: Experimental
>> +
>> +A soft real-time CPU scheduler built to provide guaranteed CPU capacity to
>> guest VMs on SMP hosts
>> +
>> +### ARINC653 Scheduler
[Cc-list modified by removing someone and adding someone else]
On Mon, 2017-09-25 at 16:10 -0700, Stefano Stabellini wrote:
> On Mon, 11 Sep 2017, George Dunlap wrote:
> > +### RTDS based Scheduler
> > +
> > +Status: Experimental
> > +
> > +A soft real-time CPU scheduler built to provide guara
On Mon, 11 Sep 2017, George Dunlap wrote:
> +### RTDS based Scheduler
> +
> +Status: Experimental
> +
> +A soft real-time CPU scheduler built to provide guaranteed CPU capacity to
> guest VMs on SMP hosts
> +
> +### ARINC653 Scheduler
> +
> +Status: Supported, Not security supported
> +
>
> +### Soft-reset for PV guests
s/PV/HVM/
> +
> +Status: Supported
> +
> +Soft-reset allows a new kernel to start 'from scratch' with a fresh VM
> state,
> +but with all the memory from the previous state of the VM intact.
> +This is primarily designed to allow "crash kernels",
> +wh
Hi,
On 12/09/2017 20:52, Stefano Stabellini wrote:
On Tue, 12 Sep 2017, Roger Pau Monné wrote:
On Mon, Sep 11, 2017 at 06:01:59PM +0100, George Dunlap wrote:
+## Scalability
+
+### 1GB/2MB super page support
+
+Status: Supported
This needs something like:
Status, x86 HVM/PVH: Supported
On Tue, 12 Sep 2017, Roger Pau Monné wrote:
> On Mon, Sep 11, 2017 at 06:01:59PM +0100, George Dunlap wrote:
> > +## Toolstack
> > +
> > +### xl
> > +
> > +Status: Supported
> > +
> > +### Direct-boot kernel image format
> > +
> > +Supported, x86: bzImage
>
> ELF
>
> > +Supported, ARM
> On Sep 11, 2017, at 13:01, George Dunlap wrote:
>
> +### XSM & FLASK
> +
> +Status: Experimental
> +
> +Compile time disabled
> +
> +### XSM & FLASK support for IS_PRIV
> +
> +Status: Experimental
In which specific areas is XSM lacking in Functional completeness, Functional
stability
On 09/11/2017 06:01 PM, George Dunlap wrote:
> Add a machine-readable file to describe what features are in what
> state of being 'supported', as well as information about how long this
> release will be supported, and so on.
>
> The document should be formatted using "semantic newlines" [1], to m
On Mon, Sep 11, 2017 at 06:01:59PM +0100, George Dunlap wrote:
> +## Toolstack
> +
> +### xl
> +
> +Status: Supported
> +
> +### Direct-boot kernel image format
> +
> +Supported, x86: bzImage
ELF
> +Supported, ARM32: zImage
> +Supported, ARM64: Image
> +
> +Format which the toolst
On Mon, Sep 11, 2017 at 06:53:55PM +0100, Andrew Cooper wrote:
> On 11/09/17 18:01, George Dunlap wrote:
> > +### x86/PV
> > +
> > +Status: Supported
> > +
> > +Traditional Xen Project PV guest
>
> What's a "Xen Project" PV guest? Just Xen here.
>
> Also, a perhaps a statement of "No hardwar
>>> On 11.09.17 at 19:53, wrote:
> As for practical limits, I don't think its reasonable to claim anything
> which we can't test. What are the specs in the MA colo?
I don't think the MA colo's limits ought to be the only ones applicable
here, and it looks like you think this way too:
>> +### Vi
On 11/09/17 19:01, George Dunlap wrote:
> Add a machine-readable file to describe what features are in what
> state of being 'supported', as well as information about how long this
> release will be supported, and so on.
>
> The document should be formatted using "semantic newlines" [1], to make
>
On 11/09/17 18:01, George Dunlap wrote:
> +### x86/PV
> +
> +Status: Supported
> +
> +Traditional Xen Project PV guest
What's a "Xen Project" PV guest? Just Xen here.
Also, a perhaps a statement of "No hardware requirements" ?
> +### x86/RAM
> +
> +Limit, x86: 16TiB
> +Limit, ARM32:
Add a machine-readable file to describe what features are in what
state of being 'supported', as well as information about how long this
release will be supported, and so on.
The document should be formatted using "semantic newlines" [1], to make
changes easier.
Signed-off-by: Ian Jackson
Signed
38 matches
Mail list logo
