> It looks like your mail client attempted to line wrap it. You might
> want to use mutt, thunderbird, or maybe even the plain text gmail
> interface to resend this.
If anyone is using Outlook, see this:
https://lkml.org/lkml/2011/1/25/587
Yuhong Bao
EFI runtime services.
In retrospect, I would have stuck with 32-bit EFI with 64-bit kernels calling
runtime services in compatibility mode, but of course it is too late for that
now.
Yuhong Bao--
To unsubscribe from this list: send the line "unsubscribe
ng to data corruption in
multitasking OSes. Let's just say that if OS/2 2.x actually replaced
DOS/Windows instead of turning into an entire fiasco, these hardware would not
likely have shipped with the problems.
Yuhong Bao--
To unsubscribe from this lis
extends this detection to
> the early page table mask.
AFAIK the only production x86-64 processor that don't support NX that I know of
is the original Nocona D0 stepping.
Must more common are the problem of BIOSes disabling the NX feature.
Yuhong Bao--
rmance and have various
> random problems. So it's not just "system stability", it's more fluid
> than that.
FYI 32-bit Windows already limits to 16GB when 3G/1G split is used for a
similar reason. (They default to 2G/2G split.)
Yuhong Bao
incorporation. so you'd need to show them that
> > it would hurt their profits to continue the way that they are going.
> I think legally bound is a myth, but that is off-topic for lkml of course.
And obviously it doesn't matter if it is actually
ink legally bound is a myth, but that is off-topic for lkml of course.
Yuhong Bao--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kerne
> + * Specifically, cr4 exists if and only if CPUID exists,
> + * which in turn exists if and only if EFLAGS.ID exists.
This may be true for *Intel* 486 CPUs as VME was implemented at the same time
as CPUID, but I am not sure that it is true for AMD 486 CPUs.
Yuho
kes me wonder what would happen if something similar was tried with EFI or
ACPI?
Yuhong Bao--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://v
> I'll contact
> the people I know in Dell and see if I can find anyone from the firmware
> division who'll actually talk to us.
What about now?
As a side note, OT, but:
http://arstechnica.com/gadgets/2014/04/fast-but-compromised-gigabytes-amd-powered-mini-gaming-pc-reviewed/?comments=1
(notice
t.
What is frustrating here is that Google decided that x86 Chromebooks should use
different firmware, otherwise it would be easier to convince vendor to fix
these firmware bugs.
Yuhong Bao--
To unsubscribe from this list: send the line "unsubscribe lin
>> I think i can go to a date based black list, that removes the manual
>> step. System running firmware before certain date assumes we need
>> to do the work around. If firmware is newer than that date, we don't
>> use the workaround. Blacklist overrides and allows current behavior
>> for new firm
Andy Lutomirski kernel.org> writes:
>
> VM86 is entirely broken if ptrace, syscall auditing, or NOHZ_FULL is
> in use. The code is a big undocumented mess, it's a real PITA to
> test, and it looks like a big chunk of vm86_32.c is dead code. It
> also plays awful games with the entry asm.
Don't
13 matches
Mail list logo
