在 2018年06月19日 22:46, lijiang 写道:
> 在 2018年06月19日 11:16, Dave Young 写道:
>> On 06/16/18 at 04:27pm, Lianbo Jiang wrote:
>>> In kdump mode, we need to dump the old memory into vmcore file,
>>> if SME is enabled in the first kernel, we must remap the old
>>> memory in encrypted manner, which will be au
在 2018年04月10日 15:47, Petr Tesarik 写道:
> On Tue, 10 Apr 2018 15:09:37 +0800
> lijiang wrote:
>
>> 在 2018年04月09日 17:40, Petr Tesarik 写道:
>> [...]
>>> Last but not least, part of the issue was probably caused by the
>>> wrong assumption that integers < 100 can be interpreted with max 3
>>> ASCII cha
Hi James, Bhupesh,
If /proc/kcore always exists in kexec/kdump, I think this issue can be fixed
easily. But it requires that Kexec/kdump have to rely on "
CONFIG_PROC_KCORE=y".
I am not sure if we can persuade Kexec-tools community to accept this.
Thanks,
Yanjiang
> -Original Message-
On Mon, Jun 18, 2018 at 11:26:11AM +0530, Bhupesh Sharma wrote:
> Hello Simon,
>
> On 05/15/2018 12:50 PM, Bhupesh Sharma wrote:
> > Hello Akashi,
> >
> > On Thu, Apr 26, 2018 at 2:27 PM, Bhupesh Sharma wrote:
> > > This patch adds the support to supply 'kaslr-seed' to secondary kernel,
> > > wh
On 06/19/2018 10:00 AM, James Morse wrote:
> Hi Dave,
>
> On 19/06/18 14:37, Dave Kleikamp wrote:
>> On 06/19/2018 01:44 AM, AKASHI Takahiro wrote:
>>> +static int __init reserve_memblock_reserved_regions(void)
>>> +{
>>> + phys_addr_t start, end, roundup_end = 0;
>>> + struct resource *mem, *
Hi Lianbo,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.17 next-20180614]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commi
Hi Lianbo,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.17 next-20180614]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commi
Hi Dave,
On 19/06/18 14:37, Dave Kleikamp wrote:
> On 06/19/2018 01:44 AM, AKASHI Takahiro wrote:
>> +static int __init reserve_memblock_reserved_regions(void)
>> +{
>> +phys_addr_t start, end, roundup_end = 0;
>> +struct resource *mem, *res;
>> +u64 i;
>> +
>> +for_each_reserved_m
在 2018年06月19日 11:16, Dave Young 写道:
> On 06/16/18 at 04:27pm, Lianbo Jiang wrote:
>> In kdump mode, we need to dump the old memory into vmcore file,
>> if SME is enabled in the first kernel, we must remap the old
>> memory in encrypted manner, which will be automatically decrypted
>> when we read f
* Required for kernel 4.17
Since kernel commit c2b4d8b7417a ("powerpc/mm/hash64: Increase the VA
range"), the max virtual (effective) address value has been increased
to 4PB. Update page table index values accordingly.
Signed-off-by: Hari Bathini
---
arch/ppc64.c |5 -
makedumpfile.h
On 06/19/2018 01:44 AM, AKASHI Takahiro wrote:
> +static int __init reserve_memblock_reserved_regions(void)
> +{
> + phys_addr_t start, end, roundup_end = 0;
> + struct resource *mem, *res;
> + u64 i;
> +
> + for_each_reserved_mem_region(i, &start, &end) {
> + if (end <
Hi James,
On Tue, Jun 19, 2018 at 4:56 PM, James Morse wrote:
> Hi Bhupesh,
>
> On 19/06/18 11:37, Bhupesh Sharma wrote:
>> On Tue, Jun 19, 2018 at 3:46 PM, James Morse wrote:
>>> On 19/06/18 10:57, Jin, Yanjiang wrote:
> -Original Message-
> From: Will Deacon [mailto:will.dea...
Hi Bhupesh,
On 19/06/18 11:37, Bhupesh Sharma wrote:
> On Tue, Jun 19, 2018 at 3:46 PM, James Morse wrote:
>> On 19/06/18 10:57, Jin, Yanjiang wrote:
-Original Message-
From: Will Deacon [mailto:will.dea...@arm.com]
Sent: 2018年6月19日 17:41
To: Jin, Yanjiang
Cc: Ja
Hi James,
On Tue, Jun 19, 2018 at 3:46 PM, James Morse wrote:
> Hi Yanjiang, Will,
>
> On 19/06/18 10:57, Jin, Yanjiang wrote:
>>> -Original Message-
>>> From: Will Deacon [mailto:will.dea...@arm.com]
>>> Sent: 2018年6月19日 17:41
>>> To: Jin, Yanjiang
>>> Cc: James Morse ; Bhupesh Sharma
>
Hi Yanjiang, Will,
On 19/06/18 10:57, Jin, Yanjiang wrote:
>> -Original Message-
>> From: Will Deacon [mailto:will.dea...@arm.com]
>> Sent: 2018年6月19日 17:41
>> To: Jin, Yanjiang
>> Cc: James Morse ; Bhupesh Sharma
>> ; Mark Rutland ; Ard
>> Biesheuvel ; Catalin Marinas
>> ; Kexec Mailing
> -Original Message-
> From: Will Deacon [mailto:will.dea...@arm.com]
> Sent: 2018年6月19日 17:41
> To: Jin, Yanjiang
> Cc: James Morse ; Bhupesh Sharma
> ; Mark Rutland ; Ard
> Biesheuvel ; Catalin Marinas
> ; Kexec Mailing List ;
> AKASHI Takahiro ; Bhupesh SHARMA
> ; linux-arm-kernel k
On Tue, Jun 19, 2018 at 09:34:56AM +, Jin, Yanjiang wrote:
> > On Tue, Jun 19, 2018 at 03:02:15AM +, Jin, Yanjiang wrote:
> > > > You seem to be using this for user-space phys_to_virt() based on
> > > > values found in /proc/iomem. This should give you what you want, and
> > > > isolate you
> -Original Message-
> From: Will Deacon [mailto:will.dea...@arm.com]
> Sent: 2018年6月19日 16:56
> To: Jin, Yanjiang
> Cc: James Morse ; Bhupesh Sharma
> ; Mark Rutland ; Ard
> Biesheuvel ; Catalin Marinas
> ; Kexec Mailing List ;
> AKASHI Takahiro ; Bhupesh SHARMA
> ; linux-arm-kernel k
On Tue, Jun 19, 2018 at 03:02:15AM +, Jin, Yanjiang wrote:
> > You seem to be using this for user-space phys_to_virt() based on values
> > found in
> > /proc/iomem. This should give you what you want, and isolate your user-space
> > from the kernel's unexpected naming of variables.
>
> I don'
This patch series is a set of bug fixes to address kexec/kdump
failures which are sometimes observed on ACPI-only system and reported
in LAK-ML before.
In short, the phenomena are:
1. kexec'ed kernel can fail to boot because some ACPI table is corrupted
by a new kernel (or other data) being loa
20 matches
Mail list logo
