Re: [RFC PATCH] acpi: indicate to platform when hot remove returns busy

Hi Andy, Thanks for your help to review my patch. On Sat, Jun 03, 2017 at 08:37:51PM +0300, Andy Shevchenko wrote: > On Sat, Jun 3, 2017 at 8:20 PM, Lee, Chun-Yi wrote: > > In hotplug logic, it always indicates non-specific failure to > > platform through _OST when

Re: [RFC PATCH] acpi: indicate to platform when hot remove returns busy

Hi Andy, Thanks for your help to review my patch. On Sat, Jun 03, 2017 at 08:37:51PM +0300, Andy Shevchenko wrote: > On Sat, Jun 3, 2017 at 8:20 PM, Lee, Chun-Yi wrote: > > In hotplug logic, it always indicates non-specific failure to > > platform through _OST when handing acpi hot-remove event

Re: [PATCH 5/5] Add a sysrq option to exit secure boot mode

Hi, On Wed, May 24, 2017 at 03:46:03PM +0100, David Howells wrote: > From: Kyle McMartin > > Make sysrq+x exit secure boot mode on x86_64, thereby allowing the running > kernel image to be modified. This lifts the lockdown. > > Signed-off-by: Kyle McMartin >

Re: [PATCH 5/5] Add a sysrq option to exit secure boot mode

Hi, On Wed, May 24, 2017 at 03:46:03PM +0100, David Howells wrote: > From: Kyle McMartin > > Make sysrq+x exit secure boot mode on x86_64, thereby allowing the running > kernel image to be modified. This lifts the lockdown. > > Signed-off-by: Kyle McMartin > Signed-off-by: David Howells >

Re: [PATCH 3/5] Add the ability to lock down access to the running kernel image

On Fri, May 26, 2017 at 01:43:12PM +0100, David Howells wrote: > Casey Schaufler wrote: > > > You called out five distinct features in 0/5, so how about > > a bit for each of those? > > Actually, there are more than five in that list - there are three in the first > item

Re: [PATCH 3/5] Add the ability to lock down access to the running kernel image

On Fri, May 26, 2017 at 01:43:12PM +0100, David Howells wrote: > Casey Schaufler wrote: > > > You called out five distinct features in 0/5, so how about > > a bit for each of those? > > Actually, there are more than five in that list - there are three in the first > item - and I'm not sure the

Re: [PATCH 4/5] efi: Lock down the kernel if booted in secure boot mode

On Wed, May 24, 2017 at 03:45:56PM +0100, David Howells wrote: > UEFI Secure Boot provides a mechanism for ensuring that the firmware will > only load signed bootloaders and kernels. Certain use cases may also > require that all kernel modules also be signed. Add a configuration option > that to

Re: [PATCH 4/5] efi: Lock down the kernel if booted in secure boot mode

On Wed, May 24, 2017 at 03:45:56PM +0100, David Howells wrote: > UEFI Secure Boot provides a mechanism for ensuring that the firmware will > only load signed bootloaders and kernels. Certain use cases may also > require that all kernel modules also be signed. Add a configuration option > that to

Re: [PATCH 3/5] Add the ability to lock down access to the running kernel image

On Wed, May 24, 2017 at 03:45:45PM +0100, David Howells wrote: > Provide a single call to allow kernel code to determine whether the system > should be locked down, thereby disallowing various accesses that might > allow the running kernel image to be changed including the loading of > modules

Re: [PATCH 3/5] Add the ability to lock down access to the running kernel image

On Wed, May 24, 2017 at 03:45:45PM +0100, David Howells wrote: > Provide a single call to allow kernel code to determine whether the system > should be locked down, thereby disallowing various accesses that might > allow the running kernel image to be changed including the loading of > modules

Re: [PATCH 2/5] efi: Add EFI_SECURE_BOOT bit

On Wed, May 24, 2017 at 03:45:32PM +0100, David Howells wrote: > From: Josh Boyer > > UEFI machines can be booted in Secure Boot mode. Add a EFI_SECURE_BOOT bit > that can be passed to efi_enabled() to find out whether secure boot is > enabled. > > This will be used

Re: [PATCH 2/5] efi: Add EFI_SECURE_BOOT bit

On Wed, May 24, 2017 at 03:45:32PM +0100, David Howells wrote: > From: Josh Boyer > > UEFI machines can be booted in Secure Boot mode. Add a EFI_SECURE_BOOT bit > that can be passed to efi_enabled() to find out whether secure boot is > enabled. > > This will be used by the SysRq+x handler,

Re: [PATCH 1/5] efi: Move the x86 secure boot switch to generic code

Hi David, On Wed, May 24, 2017 at 03:45:25PM +0100, David Howells wrote: > Move the switch-statement in x86's setup_arch() that inteprets the > secure_boot boot parameter to generic code. > > Suggested-by: Ard Biesheuvel > Signed-off-by: David Howells

Re: [PATCH 1/5] efi: Move the x86 secure boot switch to generic code

Hi David, On Wed, May 24, 2017 at 03:45:25PM +0100, David Howells wrote: > Move the switch-statement in x86's setup_arch() that inteprets the > secure_boot boot parameter to generic code. > > Suggested-by: Ard Biesheuvel > Signed-off-by: David Howells I reviewed the context for this patch.

Re: [PATCH v2] x86/efi: Disable runtime services on kexec kernel if booted with efi=old_map

On Tue, May 16, 2017 at 06:14:23PM -0700, Sai Praneeth Prakhya wrote: > From: Sai Praneeth > > Booting kexec kernel with "efi=old_map" in kernel command line hits > kernel panic as shown below. > > [0.001000] BUG: unable to handle kernel paging request at

Re: [PATCH v2] x86/efi: Disable runtime services on kexec kernel if booted with efi=old_map

On Tue, May 16, 2017 at 06:14:23PM -0700, Sai Praneeth Prakhya wrote: > From: Sai Praneeth > > Booting kexec kernel with "efi=old_map" in kernel command line hits > kernel panic as shown below. > > [0.001000] BUG: unable to handle kernel paging request at 88007fe78070 > [0.001000] IP:

Re: [PATCH] x86/efi: Fix kexec kernel panic when efi=old_map is enabled

On Mon, May 08, 2017 at 12:25:23PM -0700, Sai Praneeth Prakhya wrote: > From: Sai Praneeth > > Booting kexec kernel with "efi=old_map" in kernel command line hits > kernel panic as shown below. > > [0.001000] BUG: unable to handle kernel paging request at

Re: [PATCH] x86/efi: Fix kexec kernel panic when efi=old_map is enabled

On Mon, May 08, 2017 at 12:25:23PM -0700, Sai Praneeth Prakhya wrote: > From: Sai Praneeth > > Booting kexec kernel with "efi=old_map" in kernel command line hits > kernel panic as shown below. > > [0.001000] BUG: unable to handle kernel paging request at 88007fe78070 > [0.001000]

Re: [PATCH 2/2] ACPI / scan: Avoid enumerating devices more than once

On Mon, Apr 17, 2017 at 01:20:48AM +0200, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > acpi_bus_attach() does not check the visited flag for devices that > have been enumerated already and some of them may be enumerated > for multiple times as a result,

Re: [PATCH 2/2] ACPI / scan: Avoid enumerating devices more than once

On Mon, Apr 17, 2017 at 01:20:48AM +0200, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > acpi_bus_attach() does not check the visited flag for devices that > have been enumerated already and some of them may be enumerated > for multiple times as a result, because some callers of >

Re: [PATCH 1/2] ACPI / scan: Apply default enumeration to devices with ACPI drivers

On Mon, Apr 17, 2017 at 01:19:50AM +0200, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > The current code in acpi_bus_attach() is inconsistent with respect > to device objects with ACPI drivers bound to them, as it allows > ACPI drivers to bind to device

Re: [PATCH 1/2] ACPI / scan: Apply default enumeration to devices with ACPI drivers

On Mon, Apr 17, 2017 at 01:19:50AM +0200, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > The current code in acpi_bus_attach() is inconsistent with respect > to device objects with ACPI drivers bound to them, as it allows > ACPI drivers to bind to device objects with existing "physical"

Re: [PATCH] ACPI: emits change uevents to all physical companion devices of container's children

Hi, On Wed, Apr 19, 2017 at 02:30:18AM +0200, Rafael J. Wysocki wrote: > On Mon, Apr 3, 2017 at 5:55 PM, Lee, Chun-Yi wrote: > > The caa73ea1 patch, "ACPI / hotplug / driver core: Handle containers > > in a special way", introduced the offline callback of acpi

Re: [PATCH] ACPI: emits change uevents to all physical companion devices of container's children

Hi, On Wed, Apr 19, 2017 at 02:30:18AM +0200, Rafael J. Wysocki wrote: > On Mon, Apr 3, 2017 at 5:55 PM, Lee, Chun-Yi wrote: > > The caa73ea1 patch, "ACPI / hotplug / driver core: Handle containers > > in a special way", introduced the offline callback of acpi container. > > In the patch

Re: [PATCH 2/3] ACPI: Remove platform devices from a bus on removal

On Wed, Apr 19, 2017 at 02:50:17PM +0800, joeyli wrote: > On Wed, Mar 22, 2017 at 06:33:24PM +0100, Joerg Roedel wrote: > > From: Joerg Roedel <jroe...@suse.de> > > > > The function acpi_bus_attach() creates platform_devices if > > this is specified by t

Re: [PATCH 2/3] ACPI: Remove platform devices from a bus on removal

On Wed, Apr 19, 2017 at 02:50:17PM +0800, joeyli wrote: > On Wed, Mar 22, 2017 at 06:33:24PM +0100, Joerg Roedel wrote: > > From: Joerg Roedel > > > > The function acpi_bus_attach() creates platform_devices if > > this is specified by the firmware. But in acpi_b

Re: [PATCH 2/3] ACPI: Remove platform devices from a bus on removal

On Wed, Mar 22, 2017 at 06:33:24PM +0100, Joerg Roedel wrote: > From: Joerg Roedel > > The function acpi_bus_attach() creates platform_devices if > this is specified by the firmware. But in acpi_bus_trim() > these devices are not removed, leaving a dangling reference > to the

Re: [PATCH 2/3] ACPI: Remove platform devices from a bus on removal

On Wed, Mar 22, 2017 at 06:33:24PM +0100, Joerg Roedel wrote: > From: Joerg Roedel > > The function acpi_bus_attach() creates platform_devices if > this is specified by the firmware. But in acpi_bus_trim() > these devices are not removed, leaving a dangling reference > to the parent device. > >

Re: [PATCH 20/24] bpf: Restrict kernel image access functions when the kernel is locked down

Hi David, First, thanks for your help to send out this series. On Wed, Apr 05, 2017 at 09:17:25PM +0100, David Howells wrote: > From: Chun-Yi Lee > > There are some bpf functions can be used to read kernel memory: > bpf_probe_read, bpf_probe_write_user and bpf_trace_printk.

Re: [PATCH 20/24] bpf: Restrict kernel image access functions when the kernel is locked down

Hi David, First, thanks for your help to send out this series. On Wed, Apr 05, 2017 at 09:17:25PM +0100, David Howells wrote: > From: Chun-Yi Lee > > There are some bpf functions can be used to read kernel memory: > bpf_probe_read, bpf_probe_write_user and bpf_trace_printk. These allow >

Re: [PATCH 11/24] uswsusp: Disable when the kernel is locked down

sure how the hibernate > >>> code can verify whether or not it is in use. > >> > >> BTW, SUSE has patches adding secure boot support to the hibernate code > >> and Jiri promised me to post them last year even. :-) > > > > Oh, thanks for a friendly pin

Re: [PATCH 11/24] uswsusp: Disable when the kernel is locked down

sure how the hibernate > >>> code can verify whether or not it is in use. > >> > >> BTW, SUSE has patches adding secure boot support to the hibernate code > >> and Jiri promised me to post them last year even. :-) > > > > Oh, thanks for a friendly pin

Re: memory hotplug and force_remove

On Fri, Mar 31, 2017 at 12:55:05PM +0200, Michal Hocko wrote: > On Fri 31-03-17 18:49:05, Joey Lee wrote: > > Hi Michal, > > > > On Fri, Mar 31, 2017 at 10:30:17AM +0200, Michal Hocko wrote: > [...] > > > @@ -241,11 +232,10 @@ static int acpi_scan_try_to_offline(struct > > > acpi_device *device)

Re: memory hotplug and force_remove

On Fri, Mar 31, 2017 at 12:55:05PM +0200, Michal Hocko wrote: > On Fri 31-03-17 18:49:05, Joey Lee wrote: > > Hi Michal, > > > > On Fri, Mar 31, 2017 at 10:30:17AM +0200, Michal Hocko wrote: > [...] > > > @@ -241,11 +232,10 @@ static int acpi_scan_try_to_offline(struct > > > acpi_device *device)

Re: memory hotplug and force_remove

Hi Michal, On Fri, Mar 31, 2017 at 10:30:17AM +0200, Michal Hocko wrote: > [Fixed up email address of Toshimitsu - the email thread starts > http://lkml.kernel.org/r/20170320192938.ga11...@dhcp22.suse.cz] > > On Tue 28-03-17 17:22:58, Rafael J. Wysocki wrote: > > On Tuesday, March 28, 2017

Re: memory hotplug and force_remove

Hi Michal, On Fri, Mar 31, 2017 at 10:30:17AM +0200, Michal Hocko wrote: > [Fixed up email address of Toshimitsu - the email thread starts > http://lkml.kernel.org/r/20170320192938.ga11...@dhcp22.suse.cz] > > On Tue 28-03-17 17:22:58, Rafael J. Wysocki wrote: > > On Tuesday, March 28, 2017

Re: memory hotplug and force_remove

On Thu, Mar 30, 2017 at 10:15:04PM +0200, Rafael J. Wysocki wrote: > On Friday, March 31, 2017 12:57:29 AM joeyli wrote: > > On Thu, Mar 30, 2017 at 06:20:34PM +0200, Michal Hocko wrote: > > > On Thu 30-03-17 10:47:52, Jiri Kosina wrote: > > > > On Tue, 28 Mar

Re: memory hotplug and force_remove

On Thu, Mar 30, 2017 at 10:15:04PM +0200, Rafael J. Wysocki wrote: > On Friday, March 31, 2017 12:57:29 AM joeyli wrote: > > On Thu, Mar 30, 2017 at 06:20:34PM +0200, Michal Hocko wrote: > > > On Thu 30-03-17 10:47:52, Jiri Kosina wrote: > > > > On Tue, 28 Mar

Re: memory hotplug and force_remove

On Thu, Mar 30, 2017 at 06:20:34PM +0200, Michal Hocko wrote: > On Thu 30-03-17 10:47:52, Jiri Kosina wrote: > > On Tue, 28 Mar 2017, Rafael J. Wysocki wrote: > > > > > > > > we have been chasing the following BUG() triggering during the > > > > > > memory > > > > > > hotremove (remove_memory):

Re: memory hotplug and force_remove

On Thu, Mar 30, 2017 at 06:20:34PM +0200, Michal Hocko wrote: > On Thu 30-03-17 10:47:52, Jiri Kosina wrote: > > On Tue, 28 Mar 2017, Rafael J. Wysocki wrote: > > > > > > > > we have been chasing the following BUG() triggering during the > > > > > > memory > > > > > > hotremove (remove_memory):

Re: [PATCH] acpi: check the online state of all children in container

On Wed, Mar 22, 2017 at 01:58:30AM +0100, Rafael J. Wysocki wrote: > On Wednesday, March 22, 2017 09:01:48 AM Lee, Chun-Yi wrote: > > Just checking the state of container is not enough to confirm that > > the whole container is offlined. > > And why is that so? > Actually there does not have

Re: [PATCH] acpi: check the online state of all children in container

On Wed, Mar 22, 2017 at 01:58:30AM +0100, Rafael J. Wysocki wrote: > On Wednesday, March 22, 2017 09:01:48 AM Lee, Chun-Yi wrote: > > Just checking the state of container is not enough to confirm that > > the whole container is offlined. > > And why is that so? > Actually there does not have

Re: memory hotplug and force_remove

On Mon, Mar 20, 2017 at 10:24:42PM +0100, Rafael J. Wysocki wrote: > On Monday, March 20, 2017 03:29:39 PM Michal Hocko wrote: > > Hi Rafael, > > Hi, > > > we have been chasing the following BUG() triggering during the memory > > hotremove (remove_memory): > > ret =

Re: memory hotplug and force_remove

On Mon, Mar 20, 2017 at 10:24:42PM +0100, Rafael J. Wysocki wrote: > On Monday, March 20, 2017 03:29:39 PM Michal Hocko wrote: > > Hi Rafael, > > Hi, > > > we have been chasing the following BUG() triggering during the memory > > hotremove (remove_memory): > > ret =

Re: [PATCH v2] acer-wmi: setup accelerometer when machine has appropriate notify event

On Tue, Dec 27, 2016 at 02:00:01PM +0200, Andy Shevchenko wrote: > On Thu, Nov 3, 2016 at 2:18 AM, Lee, Chun-Yi wrote: > > The accelerometer event relies on on the ACERWMID_EVENT_GUID notify. > > So, this patch changes the codes to setup accelerometer input device > >

Re: [PATCH v2] acer-wmi: setup accelerometer when machine has appropriate notify event

On Tue, Dec 27, 2016 at 02:00:01PM +0200, Andy Shevchenko wrote: > On Thu, Nov 3, 2016 at 2:18 AM, Lee, Chun-Yi wrote: > > The accelerometer event relies on on the ACERWMID_EVENT_GUID notify. > > So, this patch changes the codes to setup accelerometer input device > > when detected

Re: [PATCH 0/4] UEFI: EFI_MEMORY_ATTRIBUTES_TABLE support for x86

Hi Sai, On Wed, Dec 07, 2016 at 12:13:28PM -0800, Sai Praneeth Prakhya wrote: > On Wed, 2016-12-07 at 20:04 +, Matt Fleming wrote: > > On Wed, 07 Dec, at 11:01:06AM, Sai Praneeth Prakhya wrote: > > > > > > Thanks Matt! > > > > > > Would you like to see a new version of these patch series

Re: [PATCH 0/4] UEFI: EFI_MEMORY_ATTRIBUTES_TABLE support for x86

Hi Sai, On Wed, Dec 07, 2016 at 12:13:28PM -0800, Sai Praneeth Prakhya wrote: > On Wed, 2016-12-07 at 20:04 +, Matt Fleming wrote: > > On Wed, 07 Dec, at 11:01:06AM, Sai Praneeth Prakhya wrote: > > > > > > Thanks Matt! > > > > > > Would you like to see a new version of these patch series

Re: [PATCH] acer-wmi: only supports AMW0_GUID1 on acer family

On Thu, Nov 03, 2016 at 11:40:15AM +0800, Anthony Wong wrote: > On 1 November 2016 at 12:30, Lee, Chun-Yi wrote: > > > > The AMW0_GUID1 wmi is not only found on Acer family but also other > > machines like Lenovo, Fujitsu and Medion. In the past days, acer-wmi > > driver

Re: [PATCH] acer-wmi: only supports AMW0_GUID1 on acer family

On Thu, Nov 03, 2016 at 11:40:15AM +0800, Anthony Wong wrote: > On 1 November 2016 at 12:30, Lee, Chun-Yi wrote: > > > > The AMW0_GUID1 wmi is not only found on Acer family but also other > > machines like Lenovo, Fujitsu and Medion. In the past days, acer-wmi > > driver handled those non-Acer

Re: [PATCH] acer-wmi: setup accelerometer when machine has appropriate notify event

Hi Darren, Thanks for your review! On Tue, Nov 01, 2016 at 10:28:51AM -0700, Darren Hart wrote: > On Tue, Nov 01, 2016 at 12:33:32PM +0800, Lee, Chun-Yi wrote: > > The accelerometer event relies on on the ACERWMID_EVENT_GUID notify. > > So, this patch changes the codes to setup accelerometer

Re: [PATCH] acer-wmi: setup accelerometer when machine has appropriate notify event

Hi Darren, Thanks for your review! On Tue, Nov 01, 2016 at 10:28:51AM -0700, Darren Hart wrote: > On Tue, Nov 01, 2016 at 12:33:32PM +0800, Lee, Chun-Yi wrote: > > The accelerometer event relies on on the ACERWMID_EVENT_GUID notify. > > So, this patch changes the codes to setup accelerometer

Re: [PATCH][v12] PM / hibernate: Verify the consistent of e820 memory map by md5 digest

Hi Chen Yu, On Thu, Oct 20, 2016 at 04:14:52PM +0800, Chen Yu wrote: > On some platforms, there is occasional panic triggered when > trying to resume from hibernation, a typical panic looks like: > > "BUG: unable to handle kernel paging request at 880085894000 > IP: []

Re: [PATCH][v12] PM / hibernate: Verify the consistent of e820 memory map by md5 digest

Hi Chen Yu, On Thu, Oct 20, 2016 at 04:14:52PM +0800, Chen Yu wrote: > On some platforms, there is occasional panic triggered when > trying to resume from hibernation, a typical panic looks like: > > "BUG: unable to handle kernel paging request at 880085894000 > IP: []

Re: [PATCH][v11] PM / hibernate: Verify the consistent of e820 memory map by md5 digest

Hi Chen Yu, On Sun, Sep 25, 2016 at 12:17:57PM +0800, Chen Yu wrote: > On some platforms, there is occasional panic triggered when trying to > resume from hibernation, a typical panic looks like: > > "BUG: unable to handle kernel paging request at 880085894000 > IP: []

Re: [PATCH][v11] PM / hibernate: Verify the consistent of e820 memory map by md5 digest

Hi Chen Yu, On Sun, Sep 25, 2016 at 12:17:57PM +0800, Chen Yu wrote: > On some platforms, there is occasional panic triggered when trying to > resume from hibernation, a typical panic looks like: > > "BUG: unable to handle kernel paging request at 880085894000 > IP: []

Re: [PATCH][v8] PM / hibernate: Verify the consistent of e820 memory map by md5 value

On Mon, Aug 29, 2016 at 03:41:23PM +0200, Borislav Petkov wrote: > On Mon, Aug 29, 2016 at 09:15:00AM +0200, Pavel Machek wrote: > > Sounds about as easy as hot unplugging arbitrary memory address. IOW > > "not easy". > > Regardless, forcibly panicking the system more is still the wrong >

Re: [PATCH][v8] PM / hibernate: Verify the consistent of e820 memory map by md5 value

On Mon, Aug 29, 2016 at 03:41:23PM +0200, Borislav Petkov wrote: > On Mon, Aug 29, 2016 at 09:15:00AM +0200, Pavel Machek wrote: > > Sounds about as easy as hot unplugging arbitrary memory address. IOW > > "not easy". > > Regardless, forcibly panicking the system more is still the wrong >

Re: [PATCH] acer-wmi: only supports AMW0_GUID1 on acer family

Hi Bjørn, On Mon, Aug 29, 2016 at 12:11:59PM +0200, Bjørn Mork wrote: > "Lee, Chun-Yi" writes: > > > The AMW0_GUID1 wmi is not only found on Acer family but also other > > machines like Lenovo, Fujitsu and Medion. In the past days, acer-wmi > > driver handled those

Re: [PATCH] acer-wmi: only supports AMW0_GUID1 on acer family

Hi Bjørn, On Mon, Aug 29, 2016 at 12:11:59PM +0200, Bjørn Mork wrote: > "Lee, Chun-Yi" writes: > > > The AMW0_GUID1 wmi is not only found on Acer family but also other > > machines like Lenovo, Fujitsu and Medion. In the past days, acer-wmi > > driver handled those non-Acer machines by quirks

Re: [PATCH][v6] PM / hibernate: Print the possible panic reason when resuming with inconsistent e820 map

On Tue, Aug 23, 2016 at 06:01:55PM +0800, Chen Yu wrote: > Hi, > thanks for your interest :) > On Tue, Aug 23, 2016 at 05:45:27PM +0800, joeyli wrote: > > Hi all, > > > > On Wed, Oct 21, 2015 at 01:21:40PM +0800, Chen Yu wrote: > > > On some platforms, ther

Re: [PATCH][v6] PM / hibernate: Print the possible panic reason when resuming with inconsistent e820 map

On Tue, Aug 23, 2016 at 06:01:55PM +0800, Chen Yu wrote: > Hi, > thanks for your interest :) > On Tue, Aug 23, 2016 at 05:45:27PM +0800, joeyli wrote: > > Hi all, > > > > On Wed, Oct 21, 2015 at 01:21:40PM +0800, Chen Yu wrote: > > > On some platforms, ther

Re: [PATCH][v6] PM / hibernate: Print the possible panic reason when resuming with inconsistent e820 map

Hi all, On Wed, Oct 21, 2015 at 01:21:40PM +0800, Chen Yu wrote: > On some platforms, there is occasional panic triggered when trying to > resume from hibernation, a typical panic looks like: > > "BUG: unable to handle kernel paging request at 880085894000 > IP: []

Re: [PATCH][v6] PM / hibernate: Print the possible panic reason when resuming with inconsistent e820 map

Hi all, On Wed, Oct 21, 2015 at 01:21:40PM +0800, Chen Yu wrote: > On some platforms, there is occasional panic triggered when trying to > resume from hibernation, a typical panic looks like: > > "BUG: unable to handle kernel paging request at 880085894000 > IP: []

Re: [PATCH] libnvdimm, nd_blk: mask off reserved status bits

Hi Ross, On Fri, Jul 29, 2016 at 02:59:12PM -0600, Ross Zwisler wrote: > The "NVDIMM Block Window Driver Writer's Guide": > > http://pmem.io/documents/ > http://pmem.io/documents/NVDIMM_DriverWritersGuide-July-2016.pdf > > defines the layout of the block window status register. For the July

Re: [PATCH] libnvdimm, nd_blk: mask off reserved status bits

Hi Ross, On Fri, Jul 29, 2016 at 02:59:12PM -0600, Ross Zwisler wrote: > The "NVDIMM Block Window Driver Writer's Guide": > > http://pmem.io/documents/ > http://pmem.io/documents/NVDIMM_DriverWritersGuide-July-2016.pdf > > defines the layout of the block window status register. For the July

Re: [PATCH] efi: capsule: allocate whole capsule into virtual memory

Hi Austin, On Fri, Jul 15, 2016 at 10:41:31AM -0600, Austin Christ wrote: > According to UEFI 2.6 section 7.5.3, the capsule should be in contiguous > virtual memory and firmware may consume the capsule immediately. To > correctly implement this functionality, the kernel driver needs to vmap >

Re: [PATCH] efi: capsule: allocate whole capsule into virtual memory

Hi Austin, On Fri, Jul 15, 2016 at 10:41:31AM -0600, Austin Christ wrote: > According to UEFI 2.6 section 7.5.3, the capsule should be in contiguous > virtual memory and firmware may consume the capsule immediately. To > correctly implement this functionality, the kernel driver needs to vmap >

Re: [PATCH v3] acpi, nfit: treat volatile virtual CD region as pmem

On Mon, Jun 27, 2016 at 10:34:32AM -0700, Dan Williams wrote: > On Sun, Jun 26, 2016 at 11:46 PM, Lee, Chun-Yi > wrote: > > This patch adds logic to treat volatile virtual CD region as pmem > > region, then /dev/pmem* device can be mounted with iso9660. > > > > It's

Re: [PATCH v3] acpi, nfit: treat volatile virtual CD region as pmem

On Mon, Jun 27, 2016 at 10:34:32AM -0700, Dan Williams wrote: > On Sun, Jun 26, 2016 at 11:46 PM, Lee, Chun-Yi > wrote: > > This patch adds logic to treat volatile virtual CD region as pmem > > region, then /dev/pmem* device can be mounted with iso9660. > > > > It's useful to work with the

Re: [PATCH v2] libnvdimm, nfit: treat volatile virtual CD region as pmem

On Sat, Jun 25, 2016 at 09:08:16AM -0700, Dan Williams wrote: > On Sat, Jun 25, 2016 at 5:21 AM, joeyli <j...@suse.com> wrote: > > iOn Fri, Jun 24, 2016 at 10:59:56AM -0700, Dan Williams wrote: > >> On Fri, Jun 24, 2016 at 12:51 AM, Lee, Chun-Yi <joeyli.ke

Re: [PATCH v2] libnvdimm, nfit: treat volatile virtual CD region as pmem

On Sat, Jun 25, 2016 at 09:08:16AM -0700, Dan Williams wrote: > On Sat, Jun 25, 2016 at 5:21 AM, joeyli wrote: > > iOn Fri, Jun 24, 2016 at 10:59:56AM -0700, Dan Williams wrote: > >> On Fri, Jun 24, 2016 at 12:51 AM, Lee, Chun-Yi > >> wrote: > >> >

Re: [PATCH v2] libnvdimm, nfit: treat volatile virtual CD region as pmem

iOn Fri, Jun 24, 2016 at 10:59:56AM -0700, Dan Williams wrote: > On Fri, Jun 24, 2016 at 12:51 AM, Lee, Chun-Yi > wrote: > > This patch adds logic to treat volatile virtual CD region as pmem > > region, then /dev/pmem* device can be mounted with iso9660. > > > > It's

Re: [PATCH v2] libnvdimm, nfit: treat volatile virtual CD region as pmem

iOn Fri, Jun 24, 2016 at 10:59:56AM -0700, Dan Williams wrote: > On Fri, Jun 24, 2016 at 12:51 AM, Lee, Chun-Yi > wrote: > > This patch adds logic to treat volatile virtual CD region as pmem > > region, then /dev/pmem* device can be mounted with iso9660. > > > > It's useful to work with the

Re: [PATCH] libnvdimm, nfit: treat volatile virtual CD region as read-only pmem

On Thu, Jun 09, 2016 at 03:34:52PM -0700, Dan Williams wrote: > On Thu, Jun 9, 2016 at 3:08 PM, Linda Knippers <linda.knipp...@hpe.com> wrote: > > On 6/4/2016 7:01 AM, joeyli wrote: > >> Hi Dan, > >> > >> Thanks for your review. > >> > >

Re: [PATCH] libnvdimm, nfit: treat volatile virtual CD region as read-only pmem

On Thu, Jun 09, 2016 at 03:34:52PM -0700, Dan Williams wrote: > On Thu, Jun 9, 2016 at 3:08 PM, Linda Knippers wrote: > > On 6/4/2016 7:01 AM, joeyli wrote: > >> Hi Dan, > >> > >> Thanks for your review. > >> > >> On Fri, Jun 03, 2016 at 12:

Re: [PATCH] libnvdimm, nfit: treat volatile virtual CD region as read-only pmem

Hi Linda, Thanks for your review and comments. On Thu, Jun 09, 2016 at 06:08:17PM -0400, Linda Knippers wrote: > On 6/4/2016 7:01 AM, joeyli wrote: > > Hi Dan, > > > > Thanks for your review. > > > > On Fri, Jun 03, 2016 at 12:27:34PM -0700, Dan Williams wrot

Re: [PATCH] libnvdimm, nfit: treat volatile virtual CD region as read-only pmem

Hi Linda, Thanks for your review and comments. On Thu, Jun 09, 2016 at 06:08:17PM -0400, Linda Knippers wrote: > On 6/4/2016 7:01 AM, joeyli wrote: > > Hi Dan, > > > > Thanks for your review. > > > > On Fri, Jun 03, 2016 at 12:27:34PM -0700, Dan Williams wrot

Re: [PATCH] libnvdimm, nfit: treat volatile virtual CD region as read-only pmem

On Sat, Jun 04, 2016 at 09:24:54AM -0700, Dan Williams wrote: > On Sat, Jun 4, 2016 at 4:01 AM, joeyli <j...@suse.com> wrote: > > Hi Dan, > > > > Thanks for your review. > > > > On Fri, Jun 03, 2016 at 12:27:34PM -0700, Dan Williams wrote: > >&g

Re: [PATCH] libnvdimm, nfit: treat volatile virtual CD region as read-only pmem

On Sat, Jun 04, 2016 at 09:24:54AM -0700, Dan Williams wrote: > On Sat, Jun 4, 2016 at 4:01 AM, joeyli wrote: > > Hi Dan, > > > > Thanks for your review. > > > > On Fri, Jun 03, 2016 at 12:27:34PM -0700, Dan Williams wrote: > >> On Fri, Jun 3, 2

Re: [PATCH] libnvdimm, nfit: treat volatile virtual CD region as read-only pmem

On Sat, Jun 04, 2016 at 09:24:54AM -0700, Dan Williams wrote: > On Sat, Jun 4, 2016 at 4:01 AM, joeyli <j...@suse.com> wrote: > > Hi Dan, > > > > Thanks for your review. > > > > On Fri, Jun 03, 2016 at 12:27:34PM -0700, Dan Williams wrote: > >&g

Re: [PATCH] libnvdimm, nfit: treat volatile virtual CD region as read-only pmem

On Sat, Jun 04, 2016 at 09:24:54AM -0700, Dan Williams wrote: > On Sat, Jun 4, 2016 at 4:01 AM, joeyli wrote: > > Hi Dan, > > > > Thanks for your review. > > > > On Fri, Jun 03, 2016 at 12:27:34PM -0700, Dan Williams wrote: > >> On Fri, Jun 3, 2

Re: [PATCH] libnvdimm, nfit: treat volatile virtual CD region as read-only pmem

Hi Dan, Thanks for your review. On Fri, Jun 03, 2016 at 12:27:34PM -0700, Dan Williams wrote: > On Fri, Jun 3, 2016 at 12:13 AM, Lee, Chun-Yi wrote: > > This patch adds codes to treat a volatile virtual CD region as a > > read-only pmem region, then read-only

Re: [PATCH] libnvdimm, nfit: treat volatile virtual CD region as read-only pmem

Hi Dan, Thanks for your review. On Fri, Jun 03, 2016 at 12:27:34PM -0700, Dan Williams wrote: > On Fri, Jun 3, 2016 at 12:13 AM, Lee, Chun-Yi wrote: > > This patch adds codes to treat a volatile virtual CD region as a > > read-only pmem region, then read-only /dev/pmem* device can be mounted >

Re: [PATCH 2/2] localmodconfig: Reset certificate paths

On Sat, Apr 02, 2016 at 10:55:22AM -0700, Benjamin Poirier wrote: > When using `make localmodconfig` and friends, if the input config comes > from a kernel that was built in a different environment (for example, the > canonical case of using localmodconfig to trim a distribution kernel > config)

Re: [PATCH 2/2] localmodconfig: Reset certificate paths

On Sat, Apr 02, 2016 at 10:55:22AM -0700, Benjamin Poirier wrote: > When using `make localmodconfig` and friends, if the input config comes > from a kernel that was built in a different environment (for example, the > canonical case of using localmodconfig to trim a distribution kernel > config)

Re: [PATCH 1/2] localmodconfig: Fix parsing of Kconfig "source" statements

On Sat, Apr 02, 2016 at 10:55:21AM -0700, Benjamin Poirier wrote: > The parameter of Kconfig "source" statements does not need to be quoted. > The current regex causes many kconfig files to be skipped and hence, > dependencies to be missed. > > Also fix the whitespace repeat count. > >

Re: [PATCH 1/2] localmodconfig: Fix parsing of Kconfig "source" statements

On Sat, Apr 02, 2016 at 10:55:21AM -0700, Benjamin Poirier wrote: > The parameter of Kconfig "source" statements does not need to be quoted. > The current regex causes many kconfig files to be skipped and hence, > dependencies to be missed. > > Also fix the whitespace repeat count. > >

Re: [PATCH] platform: acer-wmi: update notice about deprecated user interface

On Mon, Oct 05, 2015 at 12:34:47PM +0200, Martin Kepplinger wrote: > Am 2015-10-05 um 12:30 schrieb joeyli: > > Hi Darren, > > > > On Sat, Oct 03, 2015 at 10:20:52AM -0700, Darren Hart wrote: > >> On Tue, Sep 29, 2015 at 05:50:32PM +0800, joeyli wrote: > >&g

Re: [PATCH] platform: acer-wmi: update notice about deprecated user interface

Hi Darren, On Sat, Oct 03, 2015 at 10:20:52AM -0700, Darren Hart wrote: > On Tue, Sep 29, 2015 at 05:50:32PM +0800, joeyli wrote: > > Hi Martin, > > > > On Tue, Sep 29, 2015 at 08:46:38AM +0200, Martin Kepplinger wrote: > > > Signed-off-by: Martin Kepplinger &

Re: [PATCH] platform: acer-wmi: update notice about deprecated user interface

On Mon, Oct 05, 2015 at 12:34:47PM +0200, Martin Kepplinger wrote: > Am 2015-10-05 um 12:30 schrieb joeyli: > > Hi Darren, > > > > On Sat, Oct 03, 2015 at 10:20:52AM -0700, Darren Hart wrote: > >> On Tue, Sep 29, 2015 at 05:50:32PM +0800, joeyli wrote: > >&g

Re: [PATCH] platform: acer-wmi: update notice about deprecated user interface

Hi Darren, On Sat, Oct 03, 2015 at 10:20:52AM -0700, Darren Hart wrote: > On Tue, Sep 29, 2015 at 05:50:32PM +0800, joeyli wrote: > > Hi Martin, > > > > On Tue, Sep 29, 2015 at 08:46:38AM +0200, Martin Kepplinger wrote: > > > Signed-off-by: Martin

Re: [PATCH] platform: acer-wmi: update notice about deprecated user interface

Hi Martin, On Tue, Sep 29, 2015 at 08:46:38AM +0200, Martin Kepplinger wrote: > Signed-off-by: Martin Kepplinger > --- > This just looks odd in the logs. Feel free to ignore it or act on it > differently ;) > > Thanks for your patch and it reminds me to remove those interfaces in acer-wmi.

Re: [PATCH] kexec: fix out of the ELF headers buffer issue in syscall kexec_file_load()

Hi Minfei, On Tue, Sep 29, 2015 at 11:50:44AM +0800, Minfei Huang wrote: > On 09/28/15 at 02:41pm, Lee, Chun-Yi wrote: > > On big machines have CPU number that's very nearly to consume whole ELF > > headers buffer that's page aligned, 4096, 8192... Then the page fault error > > randomly

Re: [PATCH] platform: acer-wmi: update notice about deprecated user interface

Hi Martin, On Tue, Sep 29, 2015 at 08:46:38AM +0200, Martin Kepplinger wrote: > Signed-off-by: Martin Kepplinger > --- > This just looks odd in the logs. Feel free to ignore it or act on it > differently ;) > > Thanks for your patch and it reminds me to remove those

Re: [PATCH] kexec: fix out of the ELF headers buffer issue in syscall kexec_file_load()

Hi Minfei, On Tue, Sep 29, 2015 at 11:50:44AM +0800, Minfei Huang wrote: > On 09/28/15 at 02:41pm, Lee, Chun-Yi wrote: > > On big machines have CPU number that's very nearly to consume whole ELF > > headers buffer that's page aligned, 4096, 8192... Then the page fault error > > randomly

Re: [PATCH] kexec: fix out of the ELF headers buffer issue in syscall kexec_file_load()

On Mon, Sep 28, 2015 at 04:07:57PM +0800, Baoquan He wrote: > On 09/28/15 at 02:41pm, Lee, Chun-Yi wrote: > > On big machines have CPU number that's very nearly to consume whole ELF > > headers buffer that's page aligned, 4096, 8192... Then the page fault error > > randomly happened. > > > > This

Re: [PATCH] kexec: fix out of the ELF headers buffer issue in syscall kexec_file_load()

Hi, On Mon, Sep 28, 2015 at 03:16:41PM +0800, Baoquan He wrote: > Hi Chun-Yi, > > On 09/28/15 at 02:41pm, Lee, Chun-Yi wrote: > > On big machines have CPU number that's very nearly to consume whole ELF > > headers buffer that's page aligned, 4096, 8192... Then the page fault error > > randomly

Re: [PATCH] kexec: fix out of the ELF headers buffer issue in syscall kexec_file_load()

Hi, On Mon, Sep 28, 2015 at 03:16:41PM +0800, Baoquan He wrote: > Hi Chun-Yi, > > On 09/28/15 at 02:41pm, Lee, Chun-Yi wrote: > > On big machines have CPU number that's very nearly to consume whole ELF > > headers buffer that's page aligned, 4096, 8192... Then the page fault error > > randomly

Re: [PATCH] kexec: fix out of the ELF headers buffer issue in syscall kexec_file_load()

On Mon, Sep 28, 2015 at 04:07:57PM +0800, Baoquan He wrote: > On 09/28/15 at 02:41pm, Lee, Chun-Yi wrote: > > On big machines have CPU number that's very nearly to consume whole ELF > > headers buffer that's page aligned, 4096, 8192... Then the page fault error > > randomly happened. > > > > This

<    1   2   3   4   5   6   7   8   >