On 2/15/19 4:35 AM, George Dunlap wrote:
>
>
>> On Feb 13, 2019, at 7:11 PM, Stefano Stabellini
>> wrote:
>>
>> On Wed, 13 Feb 2019, Wei Liu wrote:
>>> On Tue, Feb 12, 2019 at 09:34:25PM -0500, Daniel P. Smith wrote:
The initial focus will be to explore and document the range of possible
On Feb 19, 2019, at 14:13, Stefano Stabellini wrote:
>
>> On Mon, 18 Feb 2019, Lars Kurth wrote:
>> On 18 Feb 2019, at 12:16, George Dunlap
>> wrote:
>>
>> On 2/18/19 12:11 PM, George Dunlap wrote:
>> On 2/18/19 12:01 PM, Andrew Cooper wrote:
>>On 18/02/2019 11:57, Wei Li
On Mon, 18 Feb 2019, Lars Kurth wrote:
> On 18 Feb 2019, at 12:16, George Dunlap
> wrote:
>
> On 2/18/19 12:11 PM, George Dunlap wrote:
> On 2/18/19 12:01 PM, Andrew Cooper wrote:
> On 18/02/2019 11:57, Wei Liu wrote:
> On Mon, Feb 18, 2019 at 11:53:15AM
> On 18 Feb 2019, at 12:16, George Dunlap wrote:
>
> On 2/18/19 12:11 PM, George Dunlap wrote:
>> On 2/18/19 12:01 PM, Andrew Cooper wrote:
>>> On 18/02/2019 11:57, Wei Liu wrote:
On Mon, Feb 18, 2019 at 11:53:15AM +, Lars Kurth wrote:
>
>> On 18 Feb 2019, at 11:30, George Dun
On 2/18/19 12:11 PM, George Dunlap wrote:
> On 2/18/19 12:01 PM, Andrew Cooper wrote:
>> On 18/02/2019 11:57, Wei Liu wrote:
>>> On Mon, Feb 18, 2019 at 11:53:15AM +, Lars Kurth wrote:
> On 18 Feb 2019, at 11:30, George Dunlap wrote:
>
> On 2/18/19 11:23 AM, Wei Liu wrote:
>>>
On 2/18/19 12:01 PM, Andrew Cooper wrote:
> On 18/02/2019 11:57, Wei Liu wrote:
>> On Mon, Feb 18, 2019 at 11:53:15AM +, Lars Kurth wrote:
>>>
On 18 Feb 2019, at 11:30, George Dunlap wrote:
On 2/18/19 11:23 AM, Wei Liu wrote:
> On Mon, Feb 18, 2019 at 11:17:56AM +, Lars
> On 18 Feb 2019, at 12:01, Andrew Cooper wrote:
>
> On 18/02/2019 11:57, Wei Liu wrote:
>> On Mon, Feb 18, 2019 at 11:53:15AM +, Lars Kurth wrote:
>>>
On 18 Feb 2019, at 11:30, George Dunlap wrote:
On 2/18/19 11:23 AM, Wei Liu wrote:
> On Mon, Feb 18, 2019 at 11:17:56
On 18/02/2019 11:57, Wei Liu wrote:
> On Mon, Feb 18, 2019 at 11:53:15AM +, Lars Kurth wrote:
>>
>>> On 18 Feb 2019, at 11:30, George Dunlap wrote:
>>>
>>> On 2/18/19 11:23 AM, Wei Liu wrote:
On Mon, Feb 18, 2019 at 11:17:56AM +, Lars Kurth wrote:
> Thank you Wei. It's interesting
> On 18 Feb 2019, at 11:57, Wei Liu wrote:
>
> On Mon, Feb 18, 2019 at 11:53:15AM +, Lars Kurth wrote:
>>
>>
>>> On 18 Feb 2019, at 11:30, George Dunlap wrote:
>>>
>>> On 2/18/19 11:23 AM, Wei Liu wrote:
On Mon, Feb 18, 2019 at 11:17:56AM +, Lars Kurth wrote:
> Thank you We
On Mon, Feb 18, 2019 at 11:53:15AM +, Lars Kurth wrote:
>
>
> > On 18 Feb 2019, at 11:30, George Dunlap wrote:
> >
> > On 2/18/19 11:23 AM, Wei Liu wrote:
> >> On Mon, Feb 18, 2019 at 11:17:56AM +, Lars Kurth wrote:
> >>> Thank you Wei. It's interesting though that the full vs HVM only
> On 18 Feb 2019, at 11:30, George Dunlap wrote:
>
> On 2/18/19 11:23 AM, Wei Liu wrote:
>> On Mon, Feb 18, 2019 at 11:17:56AM +, Lars Kurth wrote:
>>> Thank you Wei. It's interesting though that the full vs HVM only is almost
>>> identical in terms of SLOC's
>>> Lars
>>
>> The cloc targe
On 2/18/19 11:23 AM, Wei Liu wrote:
> On Mon, Feb 18, 2019 at 11:17:56AM +, Lars Kurth wrote:
>> Thank you Wei. It's interesting though that the full vs HVM only is almost
>> identical in terms of SLOC's
>> Lars
>
> The cloc target counts the files in the dependency graph generated by
> make.
On Mon, Feb 18, 2019 at 11:17:56AM +, Lars Kurth wrote:
> Thank you Wei. It's interesting though that the full vs HVM only is almost
> identical in terms of SLOC's
> Lars
The cloc target counts the files in the dependency graph generated by
make. A lot of the files contain both common x86 cod
Thank you Wei. It's interesting though that the full vs HVM only is almost
identical in terms of SLOC's
Lars
> On 18 Feb 2019, at 11:12, Wei Liu wrote:
>
> On Fri, Feb 15, 2019 at 11:08:41AM -0800, Stefano Stabellini wrote:
> [...]
>>>
>>> Not sure how Stefano got the 157k number. Here are som
On Fri, Feb 15, 2019 at 11:08:41AM -0800, Stefano Stabellini wrote:
[...]
> >
> > Not sure how Stefano got the 157k number. Here are some results from
> > staging.
>
> See my attached .config
I see. So these are non-debug builds. I have rerun with your config.
* HVM only -- Stefano's config
cl
On Fri, 15 Feb 2019, Wei Liu wrote:
> On Thu, Feb 14, 2019 at 09:03:24PM +, Lars Kurth wrote:
> >
> >
> > > On 14 Feb 2019, at 18:32, Stefano Stabellini
> > > wrote:
> > >
> > > On Thu, 14 Feb 2019, Jan Beulich wrote:
> > > On 13.02.19 at 20:11, wrote:
> > >>> On Wed, 13 Feb 2019, Wei
On Fri, 15 Feb 2019, George Dunlap wrote:
> > On Feb 15, 2019, at 5:36 PM, Stefano Stabellini
> > wrote:
> >
> > On Fri, 15 Feb 2019, George Dunlap wrote:
> >>> On Feb 13, 2019, at 7:11 PM, Stefano Stabellini
> >>> wrote:
> >>>
> >>> On Wed, 13 Feb 2019, Wei Liu wrote:
> On Tue, Feb 12,
> On Feb 15, 2019, at 5:36 PM, Stefano Stabellini
> wrote:
>
> On Fri, 15 Feb 2019, George Dunlap wrote:
>>> On Feb 13, 2019, at 7:11 PM, Stefano Stabellini
>>> wrote:
>>>
>>> On Wed, 13 Feb 2019, Wei Liu wrote:
On Tue, Feb 12, 2019 at 09:34:25PM -0500, Daniel P. Smith wrote:
> Gre
On Fri, 15 Feb 2019, George Dunlap wrote:
> > On Feb 13, 2019, at 7:11 PM, Stefano Stabellini
> > wrote:
> >
> > On Wed, 13 Feb 2019, Wei Liu wrote:
> >> On Tue, Feb 12, 2019 at 09:34:25PM -0500, Daniel P. Smith wrote:
> >>> Greetings,
> >>>
> >>> On the 11/14/18 Xen x86 community call a discus
On Fri, 15 Feb 2019, Jan Beulich wrote:
> >>> On 14.02.19 at 19:32, wrote:
> > Do you have any other suggestions about things that could be removed to
> > reach down to 100K LOC, in addition to what you have already written
> > above (Intel/AMD, shadow)?
>
> If you mean ones we already have Kconf
> On 15 Feb 2019, at 09:35, George Dunlap wrote:
>
>>>
>>> As use case goes, it would be a good start if you just submit something
>>> you care about.
>>
>> I mentioned on the call that a good first start could be a kconfig that
>> allows to build an hypervisor binary with only support for PV
On Thu, Feb 14, 2019 at 09:03:24PM +, Lars Kurth wrote:
>
>
> > On 14 Feb 2019, at 18:32, Stefano Stabellini wrote:
> >
> > On Thu, 14 Feb 2019, Jan Beulich wrote:
> > On 13.02.19 at 20:11, wrote:
> >>> On Wed, 13 Feb 2019, Wei Liu wrote:
> On Tue, Feb 12, 2019 at 09:34:25PM -0500
On Thu, Feb 14, 2019 at 10:32:31AM -0800, Stefano Stabellini wrote:
>
> Do you have any other suggestions about things that could be removed to
> reach down to 100K LOC, in addition to what you have already written
> above (Intel/AMD, shadow)?
Turning off some of the decompression algorithms can
> On Feb 13, 2019, at 7:11 PM, Stefano Stabellini
> wrote:
>
> On Wed, 13 Feb 2019, Wei Liu wrote:
>> On Tue, Feb 12, 2019 at 09:34:25PM -0500, Daniel P. Smith wrote:
>>> Greetings,
>>>
>>> On the 11/14/18 Xen x86 community call a discussion was initiated about
>>> using Kconfig to build mini
>>> On 14.02.19 at 19:32, wrote:
> Do you have any other suggestions about things that could be removed to
> reach down to 100K LOC, in addition to what you have already written
> above (Intel/AMD, shadow)?
If you mean ones we already have Kconfig options for, then you
could drop TBOOT, which in
>>> On 14.02.19 at 19:57, wrote:
> There is only really one interrupt controller in x86, and it hasn't
> changed much since the 486.
Well, restricting ourselves to just x2APIC would perhaps remove
some code, but not all that much.
Jan
___
Xen-devel
> On 14 Feb 2019, at 18:32, Stefano Stabellini wrote:
>
> On Thu, 14 Feb 2019, Jan Beulich wrote:
> On 13.02.19 at 20:11, wrote:
>>> On Wed, 13 Feb 2019, Wei Liu wrote:
On Tue, Feb 12, 2019 at 09:34:25PM -0500, Daniel P. Smith wrote:
> Greetings,
>
> On the 11/14/18 Xen x
On 14/02/2019 18:32, Stefano Stabellini wrote:
> On Thu, 14 Feb 2019, Jan Beulich wrote:
> On 13.02.19 at 20:11, wrote:
>>> On Wed, 13 Feb 2019, Wei Liu wrote:
On Tue, Feb 12, 2019 at 09:34:25PM -0500, Daniel P. Smith wrote:
> Greetings,
>
> On the 11/14/18 Xen x86 community c
On 14/02/2019 09:53, Jan Beulich wrote:
On 13.02.19 at 20:11, wrote:
>> On Wed, 13 Feb 2019, Wei Liu wrote:
>>> On Tue, Feb 12, 2019 at 09:34:25PM -0500, Daniel P. Smith wrote:
Greetings,
On the 11/14/18 Xen x86 community call a discussion was initiated about
using Kconfig
On Thu, 14 Feb 2019, Jan Beulich wrote:
> >>> On 13.02.19 at 20:11, wrote:
> > On Wed, 13 Feb 2019, Wei Liu wrote:
> >> On Tue, Feb 12, 2019 at 09:34:25PM -0500, Daniel P. Smith wrote:
> >> > Greetings,
> >> >
> >> > On the 11/14/18 Xen x86 community call a discussion was initiated about
> >> > u
>>> On 13.02.19 at 20:11, wrote:
> On Wed, 13 Feb 2019, Wei Liu wrote:
>> On Tue, Feb 12, 2019 at 09:34:25PM -0500, Daniel P. Smith wrote:
>> > Greetings,
>> >
>> > On the 11/14/18 Xen x86 community call a discussion was initiated about
>> > using Kconfig to build minimized versions of Xen for se
On Wed, 13 Feb 2019, Wei Liu wrote:
> On Tue, Feb 12, 2019 at 09:34:25PM -0500, Daniel P. Smith wrote:
> > Greetings,
> >
> > On the 11/14/18 Xen x86 community call a discussion was initiated about
> > using Kconfig to build minimized versions of Xen for security, safety
> > and other certificatio
On Tue, Feb 12, 2019 at 09:34:25PM -0500, Daniel P. Smith wrote:
> Greetings,
>
> On the 11/14/18 Xen x86 community call a discussion was initiated about
> using Kconfig to build minimized versions of Xen for security, safety
> and other certification requirements. After some offline discussions
>
>>> On 13.02.19 at 03:34, wrote:
> The initial focus will be to explore and document the range of possible
> use cases that are of interest to the Xen community. This will be the
> input to a design document that is crafted in conjunction with the Xen
> maintainers, to identify possible approaches
Greetings,
On the 11/14/18 Xen x86 community call a discussion was initiated about
using Kconfig to build minimized versions of Xen for security, safety
and other certification requirements. After some offline discussions
with Xen contributors I realized that a variety of efforts each with
their o
35 matches
Mail list logo
