On Wed, 25 Feb 2009 14:15:37 +0100
Thorsten Leemhuis wrote:
> On 25.02.2009 13:27, Chris Lalancette wrote:
> > Gerd Hoffmann wrote:
> >> We can also simply do this:
> >>
> >> - Install PAE kernel if the CPU supports PAE.
> >>
> >> i.e. make PAE the default kernel.
> >
> > Yes, I really think we
Thorsten Leemhuis wrote:
> On 25.02.2009 13:27, Chris Lalancette wrote:
>> Gerd Hoffmann wrote:
>>> We can also simply do this:
>>>
>>> - Install PAE kernel if the CPU supports PAE.
>>>
>>> i.e. make PAE the default kernel.
>> Yes, I really think we should just do this. It's simple, it means we g
On 25.02.2009 13:27, Chris Lalancette wrote:
Gerd Hoffmann wrote:
We can also simply do this:
- Install PAE kernel if the CPU supports PAE.
i.e. make PAE the default kernel.
Yes, I really think we should just do this. It's simple, it means we get the
logic right for Xen as well as bare-met
Gerd Hoffmann wrote:
> We can also simply do this:
>
> - Install PAE kernel if the CPU supports PAE.
>
> i.e. make PAE the default kernel.
Yes, I really think we should just do this. It's simple, it means we get the
logic right for Xen as well as bare-metal (without any special cases), and the
Will Woods wrote:
> (PAE_flag and >=4GB RAM) or (PAE_flag and vmx_flag and >=1GB RAM)
>
> where vmx_flag is the flag for hardware virt stuff. Is this a good test?
No.
> Some further questions:
> - Is a PAE kernel required for proper virt support?
Xen stopped supporting non-PAE (paravirt) guest
On Tue, 24 Feb 2009 15:38:42 -0800 (PST)
Roland McGrath wrote:
> > If we have NX (which anything made in the last few years will)
> > it's a performance win to use the hardware NX instead of the
> > segment limit hack we implemented in execshield.
>
> It's more than performance. The segment lim
> If we have NX (which anything made in the last few years will)
> it's a performance win to use the hardware NX instead of the
> segment limit hack we implemented in execshield.
It's more than performance. The segment limit hack is a hack, and does not
actually do full enforcement in all cases (
On Tue, Feb 24, 2009 at 06:22:00PM -0500, Will Woods wrote:
> On Fri, 2009-02-06 at 10:19 -0500, Bill Nottingham wrote:
> > Chris Lalancette (clala...@redhat.com) said:
> > > Do we know if anaconda is going to change
> > > to choose kernel-PAE for any machine with the PAE flag, regardless of
> - Should we be using the PAE kernel *regardless* of memory size (as
> implied above) or do we want some memory requirements?
It's always preferable on hardware (where pae actually works) that also has
the nx cpu feature. True PROT_EXEC enforcement (NX) is only available in
PAE mode.
Thanks,
R
On Fri, 2009-02-06 at 10:19 -0500, Bill Nottingham wrote:
> Chris Lalancette (clala...@redhat.com) said:
> > Do we know if anaconda is going to change
> > to choose kernel-PAE for any machine with the PAE flag, regardless of the
> > amount
> > of memory?
>
> That's the plan - the patch should be
10 matches
Mail list logo