From: Huang Ying <[EMAIL PROTECTED]>
This is another solution to implement multithreaded device matching
(probing). The device matching is delayed until all drivers are
registered. The driver registering is executed one by one, this
eliminates the potential of interdependency between drive
probes?
If subsystem needs strictly serial probing, it can accomplish this
through "depend" field as mentioned above.
>> +EXPORT_SYMBOL_GPL(device_match_freeze);
>> +EXPORT_SYMBOL_GPL(device_match_thaw);
>
>Their definitions lack kerneldoc comments.
Sorry, I will add
ive, the driver core doesn't.
I totally agree that the parallelized probing should be controlled by
the subsystems. By if the mechanism can be provided by driver core
effectively, the solution will be ideal.
Best Regards,
Huang Ying
-
To unsubscribe from this list: send the line "unsubscrib
verification. It can work on my thinkpad
T42. More optimization can be done if necessary. Because I have only
"Outlook" as mail client, the format of patch may have some problem. If
the patch has any problem and you need the patch, I can resend it in
attach file.
Best Regards,
Huang Ying
In
> > Index: linux-2.6.22-rc4/include/linux/device.h
> > ===
> > --- linux-2.6.22-rc4.orig/include/linux/device.h2007-06-08
> > 18:26:11.0 +0800
> > +++ linux-2.6.22-rc4/include/linux/device.h 2007-06-09
> >
swsusp is the default
implementation.
Signed-off-by: Huang Ying <[EMAIL PROTECTED]>
Kexec jump
This patch provide the kexec based implementation of hibernation image
operation. Now, only jumping between original kernel and kexeced
kernel is supported, real image write/read/check will be provi
This patch make it possible to have multiple implementations of
hibernation image operations such as write, read, check, etc, and they
can be switched at run time through writing the
"/sys/power/hibernation_image_ops". The uswsusp is the default
implementation.
Signed-off-by: Huang Yi
This patch provide the kexec based implementation of hibernation image
operation. Now, only jumping between original kernel and kexeced
kernel is supported, real image write/read/check will be provided in
next patches.
Signed-off-by: Huang Ying <[EMAIL PROTECTED]>
arch/i386/kernel/Ma
of kexec kernel. Maybe the kexec kernel can
be hibernate/resume by the normal kernel too. This way, a real
kexec/boot-up is only needed for the first time.
Best Regards,
Huang, Ying
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EM
overflow\n");
> > + strcat(cmdline, str);
> > +#if 0
> > + printf("Command line after adding backup\n");
> > + printf("%s\n", cmdline);
> > +#endif
> > + return 0;
> > +}
>
> printf()? ...and pleas
n't you want to suspend them, to make sure
> they're not still DMAing memory while B is trying to shuffle everything
> off to disk?
The devices should be put quiescent state to stop DMA like things. But
they do not need to be put in low power state.
"Do not put devices into low pow
es, as that of most desktop distributions. So just
"insmod" needed modules only in hibernate kernel is sufficient.
Best Regards,
Huang Ying
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
prefer it not be hooked into hibernation infrastructure.
Yes. In fact, with device_suspend(...), disable_nonboot_cpus() and
enable_nonboot_cpus(), device_resume(...) around the above two
functions, the jumping between normal kernel and kexeced kernel can work
too. Maybe it is more approriate not
a program other than main kernel. For example, for a specific
mobile device product (Such as Intel MID), a customized ultra-small
program (or kernel) can be composed to write/read image. That way, the
hibernate/resume time can be reduced to minimal.
Best Regards,
Huang Ying
-
To unsubscribe from this
ate_kernel.S.
Best Regards,
Huang Ying
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
all of the code so
> it should be relatively straight forward.
Just not loading unnecessary drivers may be sufficient. But further
optimization is also possible.
The basic idea of optimization is:
For first run:
1. boot the normal kernel A
2. kexec the hibernate kernel B
3. jump back to kernel A
are still many steps should be
done to get hibernation work.
> ...video does not work in the kexec-ed kernel, unless I boot with
> vga=1.
>
I will check it.
Best Regards,
Huang Ying
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
suming process will
continue in kexeced resuming kernel.
Best Regards,
Huang Ying
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
gt;
> Well, I don't know why this needs to be that complicated. We already have
> code in the mainline that's able to load a large hibernation image into memory
> and jump to the kernel being restored. And it has _no_ 50% of RAM limitation,
> this is the _saving_ part of the current code t
The changelog between v1 and v2
1. The kexec jump implementation is put into the kexec/kdump
framework instead of software suspend framework. The device
and CPU state save/restore code of software suspend is called
when needed.
2. The same code path is used for both kexec a new kernel
is called to implement corresponding function.
Signed-off-by: Huang Ying <[EMAIL PROTECTED]>
---
arch/i386/Kconfig|7 +++
arch/i386/kernel/Makefile|1
arch/i386/kernel/kexec_jump.S| 74 +
arch/i386/kernel/machine_kexec.c
freely during image writing/reading.
On x86_64, there is another usage of nosave during processing E820
memory map. But I don't know why the memory region other than E820_RAM
are marked as nosave. I think only the memory region of type E820_RAM
will be thought of normal memory, others will be though
boration?
At last, thank you very much for your valuable reminding in the mail of
"hibernation considerations".
Best Regards,
Huang Ying
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
think this is easy to be
implemented. And the serialization demand between subsystem can be
satisfied too.
> > + * @probe: probing infromation include probing function and parameter
> ^^^
> typo: information
Sorry, I will correct it in the next ver
ing patch. If I need do
anything because of it, please let me know.
Any comment is welcome.
Best Regards,
Huang Ying
---
This patch add multithreaded probing with more parallelism control.
The device/driver probing is done on a probing queue, which is a
customized version of work queue, where the
w kthread for this. And the bus scanning thread may need to exist
during system running, using the probing queue the bus scanning thread
can be created and destroyed on demanded too.
Thank you very much for your comment.
Best Regards,
Huang Ying
-
To unsubscribe from this list: send the line "
time, while with workqueue, just schedule the jobs needed.
And a workqueue like the probing queue whose thread can be
created/destroyed on demand will save more resources than ordinary
workqueue. :)
Best Regards,
Huang Ying
-
To unsubscribe from this list: send the line "unsubscribe linux-ker
can be
used for this. The parallel control mechanism can be used to implement
multithreaded device probing in needed subsystems too.
Best Regards,
Huang, Ying
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
ibernate kernel to pass information back to
pre-hibernate kernel. For example, the information can be passed in jump
buffer page.
Best Regards,
Huang Ying
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
uspend. Without that, the ACPI
issue can not be resolved.
Best Regards,
Huang Ying
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at ht
k in a file. This means
> you could save the booted save kernel, it just couldn't have any shared
> storage open.
Yes, this is also in plan. But with lower priority and will only be
added if necessary.
Best Regards,
Huang Ying
-
To unsubscribe from this list: send the line "unsubscrib
implementation in
> > "relocate_kernel".
>
> what do you mean by "scatter swap"
copy: dest=src
swap: tmp=dest; dest=src; src=tmp
If memory is swapped, no information is lost, both that of kexec kernel
and kexeced kernel.
Best Regards,
Huang, Ying
-
To unsubs
On Thu, 2007-08-16 at 06:42 +0800, Andrew Morton wrote:
> On Mon, 13 Aug 2007 15:30:19 +0800
> "Huang, Ying" <[EMAIL PROTECTED]> wrote:
>
> > Following sets of patches add EFI/UEFI (Unified Extensible Firmware
> > Interface) runtime services support to x86_
On Thu, 2007-08-16 at 07:16 +0800, Andrew Morton wrote:
> On Mon, 13 Aug 2007 15:30:19 +0800
> "Huang, Ying" <[EMAIL PROTECTED]> wrote:
>
> > Following sets of patches add EFI/UEFI (Unified Extensible Firmware
> > Interface) runtime services support to
On Thu, 2007-08-16 at 07:22 +0800, H. Peter Anvin wrote:
> Andrew Morton wrote:
> > On Mon, 13 Aug 2007 15:30:19 +0800
> > "Huang, Ying" <[EMAIL PROTECTED]> wrote:
> >
> >> Following sets of patches add EFI/UEFI (Unified Extensible Firmware
>
On Thu, 2007-08-16 at 16:11 +0200, Andi Kleen wrote:
> Huang, Ying wrote:
> > On Thu, 2007-08-16 at 06:42 +0800, Andrew Morton wrote:
> >> On Mon, 13 Aug 2007 15:30:19 +0800
> >> "Huang, Ying" <[EMAIL PROTECTED]> wrote:
> >>
> >>> Fol
age tables are cleared, the corresponding page is executable
(refer to section 4.13.2 of Intel 64 and IA-32 Architectures Software
Developer's Manual). So, the bug is fixed through clearing the "NX"
bit of PMD when splitting the huge PMD.
Signed-off-by: Huang Ying <[EMAIL PROTECTED]>
---
I
t, but got lots of scary rejects.
>
> Is there chance for a patch against kexec-testing?
I have some other work to do recently. So the next version will delay
for some while. :(
But now, I have a patch against kexec-tools-testing.
Best Regards,
Huang Ying
Index: kexec-tools/kexec/arch
On Fri, 2007-08-17 at 09:11 -0700, H. Peter Anvin wrote:
> Huang, Ying wrote:
> >>
> >> Has the zero page documentation and version numbering project
> >> made any progress? I think we cannot merge this without at least
> >> the version number
> >
>
On Sun, 2007-08-19 at 16:25 -0600, Eric W. Biederman wrote:
> "Huang, Ying" <[EMAIL PROTECTED]> writes:
> >> > +#define EFI_LOADER_SIG ((unsigned char *)(PARAM+0x1c0))
> >> > +#define EFI_MEMDESC_SIZE (*((unsigned int *) (PARAM+0x1c4)))
> >
On Mon, 2007-08-20 at 10:12 -0700, H. Peter Anvin wrote:
> Huang, Ying wrote:
> >>
> >> I propose that, in addition to the aforementioned version number and
> >> magic fields, we add a pointer, which should be the last pointer added
> >> that doesn't point
On Mon, 2007-08-20 at 20:54 -0700, H. Peter Anvin wrote:
> Huang, Ying wrote:
> >
> > I think the "next" field can be u32 instead of u64. Because the linked
> > list of struct setup_data is prepared by bootloader, which can control
> > the memory location
o -mm and
> kexec-testing?
Now I have worked out a full kexec based hibernation prototype,
including kexec, write out the image, reboot, restore the memory and
jump back. I will release it recently. :)
Best Regards,
Huang Ying
-
To unsubscribe from this list: send the line "unsubscribe linux-k
ge protocol can
boot the new kernel, because the "zero page" protocol is kept for
short term. New version of bootloader should use "linked list"
protocol instead of "zero page" protocol.
In the future, when all bootloaders use new protocol, the "zero page"
is m
On Thu, 2007-08-23 at 00:28 +0800, H. Peter Anvin wrote:
> huang ying wrote:
> >
> > My proposal: Use Peter proposed "linked list of struct setup_data"
> > style boot protocol as long term goal.
> >
> > To smooth the transforming process, the follow
heckpatch.pl will save me work.
Sorry, the next version will be checked with checkpatch.pl firstly.
> > +#ifndef __i386__
> > + //screen_info.imacpm_seg = 0;
> > +#endif
>
> hmm.
>
> > +
> > + if (!request_mem_region(efifb_fix.smem_start,
+{
> > + u64 ret, dummy;
> > + register u64 r8 __asm__("r8");
> > + register u64 r9 __asm__("r9");
> > + register u64 r10 __asm__("r10");
> > + register u64 r11 __asm__("r11");
> > + __asm__ __volatile__(
Kexec base hibernation has some potential advantages over uswsusp and
TuxOnIce (suspend2). Some most obvious advantages are:
1. The hibernation image size can exceed half of memory size easily.
2. The hibernation image can be written to and read from almost
anywhere, such as USB disk, NFS.
, the state of devices and CPU are restored
accordingly. The devices/CPU state save/restore code of software
suspend is called to implement corresponding function.
Signed-off-by: Huang Ying <[EMAIL PROTECTED]>
---
Documentation/kernel-parameters.txt |8 +++
arch/i386/K
This patch adds writing support for /dev/oldmem. This is used to
restore the memory contents of hibernated system.
Signed-off-by: Huang Ying <[EMAIL PROTECTED]>
---
arch/i386/kernel/crash_dump.c | 27 +++
drivers/char/mem.c
der directly.
Best Regards,
Huang Ying
> Best regards
> Hu, Fenghua
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Huang, Ying
> Sent: 2007年8月27日 9:14
> To: Eric W. Biederman; Pavel Machek; [EMAIL PROTECTED]; Andrew Morton; Jer
On Mon, 2007-08-27 at 10:30 +0530, Vivek Goyal wrote:
> On Mon, Aug 27, 2007 at 09:14:05AM +0800, Huang, Ying wrote:
> > Kexec base hibernation has some potential advantages over uswsusp and
> > TuxOnIce (suspend2). Some most obvious advantages are:
> >
> > 1. The
, that may be a bit of problem for a bootloader,
> but I'm glad bootloaders are bloated already :-).
As far as I know, the grub 2.0 uses a modular implementation scheme.
That is, every OS loader (Multi-boot, Linux, FreeBSD etc), partition
table, file system is implemented as a module, and these module
On Mon, 2007-08-27 at 23:31 +0200, Pavel Machek wrote:
> Hi!
>
> > This patch adds writing support for /dev/oldmem. This is used to
> > restore the memory contents of hibernated system.
> >
> > Signed-off-by: Huang Ying <[EMAIL PROTECTED]>
>
> >
er jumping
> > back from kexeced kernel, the state of devices and CPU are restored
> > accordingly. The devices/CPU state save/restore code of software
> > suspend is called to implement corresponding function.
> >
> > Signed-off-by: Huang Ying <[EMAIL PROTECTED]>
&g
.
3. When devices are quiesced, they are put into "low power" state and
system is put into suspend state; or the image is written to disk
(through snapshot/uswsusp or kexeced kernel).
4. After resuming from RAM/DISK, devices are put into "normal" state and
the syscall entries replaced in
gion" concepts with
"iomem_resource" (maybe need some enhancement).
Best Regards,
Huang Ying
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
that can be revisited with code consolidation
across architectures.
Looking forward to your comments,
Best Regards,
Huang Ying
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.
the firmware service.
Signed-off-by: Chandramouli Narayanan <[EMAIL PROTECTED]>
Signed-off-by: Huang Ying <[EMAIL PROTECTED]>
---
arch/x86_64/Kconfig | 13
arch/x86_64/kernel/Makefile |1
arch/x86_64/kernel/efi.c | 507
runtime service area so that EFI runtime code is
executable.
Signed-off-by: Chandramouli Narayanan <[EMAIL PROTECTED]>
Signed-off-by: Huang Ying <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/aperture.c |5 +
arch/x86_64/kernel/e820.c |8
arch/x86_64/kernel/setup.
-by: Chandramouli Narayanan <[EMAIL PROTECTED]>
Signed-off-by: Huang Ying <[EMAIL PROTECTED]>
---
reboot.c | 11 ++-
time.c | 47 +++
2 files changed, 41 insertions(+), 17 deletions(-)
Index: linux-2.6.23-rc1/arch/x86_64/ker
ed-off-by: Huang Ying <[EMAIL PROTECTED]>
---
i386/zero-page.txt | 18 ++
x86_64/uefi.txt| 42 ++
2 files changed, 56 insertions(+), 4 deletions(-)
Index: linux-2.6.23-rc1/Documentation/i386/z
the video information as
appropriate for EFI firmware.
Signed-off-by: Chandramouli Narayanan <[EMAIL PROTECTED]>
Signed-off-by: Huang Ying <[EMAIL PROTECTED]>
---
drivers/video/Kconfig | 11 ++
drivers/video/Makefile |1
drivers/video/efifb.c
On Mon, 2007-07-30 at 22:34 -0600, Eric W. Biederman wrote:
> "Huang, Ying" <[EMAIL PROTECTED]> writes:
>
> > This patch adds Graphics Output Protocol support to the kernel.
> > UEFI2.0 spec deprecates Universal Graphics Adapter (UGA) protocol and
>
On Mon, 2007-07-30 at 22:40 -0600, Eric W. Biederman wrote:
> "Huang, Ying" <[EMAIL PROTECTED]> writes:
>
> > This patch adds document for EFI x86_64 support. The boot parameters
> > added are documented in Documentation/i386/zero-page.txt. The setup
> >
On Mon, 2007-07-30 at 22:37 -0600, Eric W. Biederman wrote:
> "Huang, Ying" <[EMAIL PROTECTED]> writes:
>
> > Changelog between v2 and v3:
> >
> > 1. The EFI callwrapper is re-implemented in assembler.
> >
> > ---
> >
> > Th
e.
For EFI based firmware, the parameter to runtime service call is the
only way to tell firmware whether a warm or cold reboot is requested.
That is not implemented by current EFI support patch yet, but we will
add it in the next version.
> > Signed-off-by: Chandramouli Narayanan <[EMAIL P
On Mon, 2007-07-30 at 22:16 -0600, Eric W. Biederman wrote:
> "Huang, Ying" <[EMAIL PROTECTED]> writes:
> > - The variable efi_enabled is used throughout across architecutres if
> > CONFIG_EFI option is enabled. The i386 code also uses this variable.
> > Th
do_sync = 1;
> > + do_ifdown = 0;
> > + do_exec = 0;
> > + do_jump = 1;
> > + break;
> > case OPT_TYPE:
> > type = optarg;
> >
and x86_64
kernel on EFI platform.
Signed-off-by: Chandramouli Narayanan <[EMAIL PROTECTED]>
Signed-off-by: Huang Ying <[EMAIL PROTECTED]>
drivers/video/Kconfig | 11 ++
drivers/video/Makefile |1
drivers/video/efifb.c
by bootloader if available.
Looking forward to your comments,
Best Regards,
Huang Ying
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FA
This patch adds document for EFI x86_64 boot support. The setup and
operation guide of EFI based system is documented in
Documentation/x86_64/uefi.txt.
Signed-off-by: Chandramouli Narayanan <[EMAIL PROTECTED]>
Signed-off-by: Huang Ying <[EMAIL PROTECTED]>
uef
cially these come from firmware) should be 64bit
to make the entry point can be used for both 32bit and 64bit platform.
3. More complete and formal document.
Can you kindly tell me what's more should be done?
Best Regards,
Huang Ying
-
To unsubscribe from this list: send the line "unsubscribe linu
ussed than just EFI->e820 conversion.
We can discuss them in another thread.
Best Regards,
Huang Ying
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
y time.
Yes, all pointers should be physical. But some pointers come from
firmware such as ACPI root pointer, EFI system table pointer should be
64bit, because we can not control the actual position pointed to.
> > 3. More complete and formal document.
> >
> > Can you kindl
Narayanan <[EMAIL PROTECTED]>
Signed-off-by: Huang Ying <[EMAIL PROTECTED]>
Index: linux-2.6.23-rc2/Documentation/i386/zero-page.txt
===
--- linux-2.6.23-rc2.orig/Documentation/i386/zero-page.txt 2007-08-13
13:08:39.000
be chosen with kernel boot options.
Signed-off-by: Chandramouli Narayanan <[EMAIL PROTECTED]>
Signed-off-by: Huang Ying <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/reboot.c| 19 -
arch/x86_64/kernel/time.c | 48 ++-
ed lin2win ( is the number of
parameters) are implemented. EFI function calls are wrapped before
calling the firmware service.
Signed-off-by: Chandramouli Narayanan <[EMAIL PROTECTED]>
Signed-off-by: Huang Ying <[EMAIL PROTECTED]>
---
arch/x86_64/Kconfig | 13
arch/
comments,
Best Regards,
Huang Ying
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Tue, 2007-07-31 at 04:52 -0600, Eric W. Biederman wrote:
> "Huang, Ying" <[EMAIL PROTECTED]> writes:
>
> > On Tue, 2007-07-31 at 11:10 +0200, Pavel Machek wrote:
> >> > Index: kexec-too
am I doing wrong?
The kexec-tools version 1.101 does not work perfectly with relocatable
kernel. This would have been solved if I worked against kexec-tools
testing tree. I will work against testing tree in the next version.
But, with some trick, it can work. When configure kernel, make sure the
following op
+
> > + kexec_jump_buf_pfn = memparse(arg, );
> > + kexec_flags |= KEXEC_FLAGS_IS_KEXECED_KERNEL;
> > + return 0;
> > +}
> > +early_param("kexec_jump_buf_pfn", parse_kexec_jump_buf_pfn);
>
> This one should be documented, too, I'd guess. (Is that
used there, because "alloc_pages" is used
by "change_page_attr".
Should I change "change_page_attr" to make it work before "mem_init"? Or
Should I change "init_memory_mapping" to make it can be used to change
mapping attributes? Which one is better?
On Wed, 2007-08-01 at 13:55 +0800, Antonino A. Daplas wrote:
> On Tue, 2007-07-31 at 11:13 +0800, Huang, Ying wrote:
>
> > +
> > +#include
> > +#include
> > +#include
> > +#include
> > +#include
> > +#include
> > +#include
>
I tried with acpi=off,
> nosmp... but problem does not seem device related.
It seems that the problem has nothing to do with device or ACPI. Can you
do a normal kexec? That is:
kexec -l <...>
kexec -e
or
kexec -p <...>
ALT-SysRq-c to trigger a crash dump.
Best Regards,
Huang Yin
service
are always mapped to same address in direct map area.
Best Regards,
Huang Ying
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
erly. So
vmlinux must be used with "-p". And the tricks previous mentioned must
be used for normal kexec -p too. The example command line is as follow:
kexec -p --args-linux vmlinux --append="root=/dev/ ..."
Best Regards,
Huang Ying
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
l. But I
think EFI runtime service is not essential in this situation, because
the raw hardware can be used too.
Best Regards,
Huang Ying
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vge
On Tue, 2007-08-07 at 11:54 +0200, Andi Kleen wrote:
> On Tuesday 07 August 2007 11:29:44 Huang, Ying wrote:
>
> > > How does EFI handle 32bit/64bit compatibility? In particular
> > > how do I load a 32bit kernel on machine with a 64bit EFI? Can
> > > it be
e EFI memory map to E820 map in "boot
parameters memory" which is copied to "boot_params" or "x86_boot_params"
by Linux kernel later.
>Or did you apply more patches?
No, just the frame buffer patch.
Best Regards,
Huang Ying
-
To unsubscribe from this list: send the l
bugs later can be worked around. Also some Documentation
> would be good. And comments. But discussion first.
>
Is what defined in Documentation/i386/zero-page.txt the standard boot
protocol. If it is, the elilo follows it. My previous expressing is
not clear and correct.
Best Regards,
Huang Yin
On Tue, 2007-09-11 at 20:23 -0700, Andrew Morton wrote:
> On Fri, 17 Aug 2007 13:28:38 +0800 "Huang, Ying" <[EMAIL PROTECTED]> wrote:
>
> > This patch fixes a bug of change_page_attr/change_page_attr_addr on
> > Intel x86_64 CPU. After changi
TE is
still there, no page will be made executable if not been set explicitly
through PTE. For AMD CPU, will the page be made executable if the NX bit
of PMD is cleared and the NX bit of PTE is set? If so, I will do the
change as you said.
> Anyways; it's really not very important.
It is needed by EFI ru
This patch add a field of 64-bit physical pointer to NULL terminated
single linked list of struct setup_data to real-mode kernel
header. This is used to define a more extensible boot parameters
passing mechanism.
Signed-off-by: Huang Ying <[EMAIL PROTECTED]>
---
arch/i386/K
This patch defines a 32-bit boot protocol and adds corresponding
document.
Signed-off-by: Huang Ying <[EMAIL PROTECTED]>
---
boot.txt | 105 ++-
1 file changed, 104 insertions(+), 1 deletion(-)
Index: linux-2.6.23-rc4/Documen
_64 kernel will overwrite some
pages from 0x1000 on.
EFI64 runtime service is the first user of 32-bit boot protocol and
boot parameters passing mechanism. To demonstrate their usage, the
EFI64 runtime service patch is also appended with the mail.
Best Regards,
Huang Ying
---
Documentation/i38
Hi, Peter,
On Wed, 2007-09-19 at 09:04 -0700, H. Peter Anvin wrote:
> Huang, Ying wrote:
> >
> > Known Issues:
> >
> > 1. Where is safe to place the linked list of setup_data?
> > Because the length of the linked list of setup_data is variable, it
>
y process
need to be run. For example, it is possible that there is only one user
process -- the image-writing process running in image-writing kernel.
So, no freezer or blkdev snapshot is needed.
Best Regards,
Huang Ying
-
To unsubscribe from this list: send the line "unsubscribe linux-ker
executing.
Signed-off-by: Huang Ying <[EMAIL PROTECTED]>
---
Documentation/i386/jump_back_protocol.txt | 103 ++
arch/powerpc/kernel/machine_kexec.c |2
arch/ppc/kernel/machine_kexec.c |2
arch/sh/kernel/machine_kexec.c|2
arch/x86/
This patch implements kexec based hibernate/resume. This is based on
the facility provided by kexec_jump. The ACPI methods are called at
specified environment to conform the ACPI specification. Two new
reboot commands are added to trigger hibernate/resume.
Signed-off-by: Huang Ying <[EM
1 - 100 of 3349 matches
Mail list logo
