Hi Peter,
> Peter Chen hat am 25. April 2017 um 10:14 geschrieben:
>
> Since you unplug the cable first, and plug in again. The driver will
> treat it as connection but not resume event. You may use
> /sys/class/udc/ci_hdrc.0/state to get udc's connection, eg "not attached"
> or other states to
Hi,
> Peter Chen hat am 24. April 2017 um 05:51 geschrieben:
> >
> The current code logic is:
> - When the resume is received from host, the ci->dirver->resume is
> called, and suspended is cleared.
> - When the reset is received from host, the isr_reset_handler is called,
> and suspended is cle
rrupt handler to set it back (and to modify it to set
ci->suspended to 0 even if ci->driver->resume is NULL).
This code works on my platform. However, since I didn't write the driver
and since I have no deep understanding of it, I cannot determine if
there are any negative side effe
>From the perspective of RESET, the meaning of the new property
is actually "active high". Thanks for Troy Kisky for pointing
that out.
Since the patch is in linux-next, this patch is incremental and doesn't
replace the original patch.
Signed-off-by: Bernhard Walle
---
Docume
It's perfectly valid to use the LTC3589 without an interrupt pin
connected to it. Currently, the driver probing fails when client->irq
is 0 (which means "no interrupt"). Don't register the interrupt
handler in that case but successfully finish the device probing instead.
Hi,
thanks for the review!
Am 10.02.2016 10:44, schrieb Philipp Zabel:
+ IRQF_TRIGGER_LOW | IRQF_ONESHOT,
+ client->name, ltc3589);
+ if (ret) {
+ dev_err(dev, "Fail
It's perfectly valid to use the LTC3589 without an interrupt pin
connected to it. Currently, the driver probing fails when client->irq
is 0 (which means "no interrupt"). Don't register the interrupt
handler in that case but successfully finish the device probing instead.
We need that for a custom hardware that needs the reverse reset
sequence.
Signed-off-by: Bernhard Walle
---
Changes compared to v1:
- Add documentation to 'phy-reset-gpios' that flags are ignored
as suggested by Andrew Lunn.
Documentation/devicetree/bindings/net/fsl-f
We need that for a custom hardware that needs the reverse reset
sequence.
Signed-off-by: Bernhard Walle
---
Documentation/devicetree/bindings/net/fsl-fec.txt | 3 +++
drivers/net/ethernet/freescale/fec_main.c | 8 ++--
2 files changed, 9 insertions(+), 2 deletions(-)
diff --git a
while performing the measurement seems to
be the better way, I think.
Signed-off-by: Bernhard Walle
---
drivers/hwmon/htu21.c | 52 +--
1 file changed, 46 insertions(+), 6 deletions(-)
diff --git a/drivers/hwmon/htu21.c b/drivers/hwmon/htu21.c
index 83
Am 2014-05-27 15:43, schrieb KY Srinivasan:
Can I provide more information to track down the problem?
This bug has been fixed upstream. The issue is with regards to the
older hosts (ws2008 r2) not
Being able to handle the larger receive buffer currently used.
Can you point me to the commit t
Hello,
using a 3.14 kernel in a Linux VM running on HyperV (Windows Server 2008
R2) we get following error:
hv_netvsc: hv_netvsc channel opened successfully
hv_netvsc vmbus_0_9 (unregistered net_device): Unable to complete receive
buffer initialization with NetVsp - status 2
hv_netvsc v
Hi,
* Ingo Molnar [2012-09-29 08:37]:
> * Jean Delvare wrote:
>
> > The correct syntax for gcc -x is "gcc -x assembler", not "gcc
> > -xassembler". Even though the latter happens to work, the
> > former is what is documented in the manual page and thus what
> > gcc wrappers such as icecream
* Andrew Morton <[EMAIL PROTECTED]> [2008-02-04 23:40]:
> We did this wrong. We should have introduced a new reserve_bootmem_foo()
> and migrated over to that in stages. Once all callers are migrated, remove
> the old interface.
Well, my original proposal was to add a new function but then someo
* Andrew Morton <[EMAIL PROTECTED]> [2008-02-04 14:04]:
>
> but that code really needs help.
Using spin_lock_irqsave() is what rtc_get_rtc_time() does which was
used before I changed to get_rtc_time() does. So it should be ok. I
missed that difference. However, I agree with you the whole RTC
"emu
* Sachin P. Sant <[EMAIL PROTECTED]> [2008-02-05 06:33]:
> Bernhard Walle wrote:
>> * Vivek Goyal <[EMAIL PROTECTED]> [2008-02-04 19:38]:
>>
>>> Bernahard, any idea who is the competitor here?
>>>
>> Hm ..., can you boot the kernel
* Vivek Goyal <[EMAIL PROTECTED]> [2008-02-04 19:38]:
>
> Bernahard, any idea who is the competitor here?
Hm ..., can you boot the kernel without crashkernel= and provide the
/proc/iomem?
Bernhard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
* Pavel Machek <[EMAIL PROTECTED]> [2007-12-21 11:17]:
> Or is crashdump only supported on i386?
No.
Thanks,
Bernhard
--
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/majordo
ns to CONFIG_RTC=y any more.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/x86/kernel/hpet.c | 47 ++-
include/asm-x86/hpet.h |3 +++
2 files changed, 49 insertions(+), 1 deletion(-)
--- a/arch/x86/kernel/hpet.c
+++ b/arch/x86/ke
se of this, it's possible to compile the drivers/char/rtc.ko driver
as module and still use the HPET emulation functionality. This is also
expressed in Kconfig.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/x86/Kconfig |2 +-
arch/x86/kernel/hpet.c |2 --
dr
plied.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
--
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 patch adds the RTC emulation of the HPET timer to the new RTC_DRV_CMOS.
The old drivers/char/rtc.ko driver had that functionality and it's important
on new systems.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/x86/Kconfig |2 -
drivers/rtc/rtc-cm
That patch adds the RTC emulation of the HPET timer to the new RTC_DRV_CMOS.
The old drivers/char/rtc.ko driver had that functionality and it's important
on new systems.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/x86/Kconfig |2 -
drivers/rtc/rtc-cm
* Bernhard Walle <[EMAIL PROTECTED]> [2007-12-20 16:24]:
...
This was an accident. The patch belongs to a patch series that I'll
post later. Please ignore!
Thanks,
Bernhard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body o
This patch is against 2.6.24-rc5-mm1.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/x86/kernel/hpet.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/arch/x86/kernel/hpet.c
+++ b/arch/x86/kernel/hpet.c
@@ -657,7 +657,7 @@ irqreturn_t hpet_rtc_interr
* Russell King <[EMAIL PROTECTED]> [2007-10-28 14:04]:
> On Sun, Oct 28, 2007 at 12:59:52PM +0100, Bernhard Walle wrote:
> > * Russell King <[EMAIL PROTECTED]> [2007-10-28 11:34]:
> > >
> > > If you go down that route, you end up with _lots_ of circular
>
* Russell King <[EMAIL PROTECTED]> [2007-10-28 11:34]:
>
> If you go down that route, you end up with _lots_ of circular
> dependencies - header file X needs Y needs Z which needs X. We've
> been there, several times. It very quickly becomes quite
> unmaintainable - you end up with hard to predi
race condition
inside reserve_bootmem_core().
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/alpha/kernel/core_irongate.c |3 ++-
arch/alpha/kernel/setup.c |5 +++--
arch/alpha/mm/numa.c |5 +++--
arch/arm/mm/init.c|4 ++--
arch/a
This patchset adds a flags variable to reserve_bootmem() and uses the
BOOTMEM_EXCLUSIVE flag in crashkernel reservation code to detect collisions
between crashkernel area and already used memory.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
This patch uses the BOOTMEM_EXCLUSIVE, introduced in the previous patch,
to avoid conflicts while reserving the memory for the kdump carpture kernel
(crashkernel=).
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/sh/kernel/setup.c | 29 ++---
ar
is the fix that was
missing, so no need to drop it now.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/alpha/kernel/core_irongate.c |3 ++-
arch/alpha/kernel/setup.c |5 +++--
arch/alpha/mm/numa.c |5 +++--
arch/arm/mm/init.c|
This patch implements the usage of BOOTMEM_EXCLUSIVE for crashkernel
reservation on other architectures. The only architecture that applies
is sh.
The patch is based on current git tree plus
kexec-introduce-bootmem_exclusive.patch from -mm tree.
Signed-off-by: Bernhard Walle <[EMAIL PROTEC
* Andrew Morton <[EMAIL PROTECTED]> [2007-10-18 23:26]:
> On Thu, 18 Oct 2007 13:15:36 +0200
> Bernhard Walle <[EMAIL PROTECTED]> wrote:
>
> > This patch adds the BSS to the resource tree just as kernel text and kernel
> > data are in the resource tree. The ma
rce are passed to
e820_reserve_resources() as arguments just as done on i386 and IA64. That also
avoids the "extern" reference and it's possible to make it static.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/x86/kernel/e820_32.c | 49
6 and
ia64).
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/ia64/kernel/efi.c |4 +++-
arch/ia64/kernel/setup.c | 14 +++---
arch/x86/kernel/e820_32.c | 18 +++---
arch/x86/kernel/e820_64.c |3 ++-
arch/x86/kernel/efi_32.c |4 +++-
arch
This means that it's only for
x86 and breaks other architectures. If the patch is ok, I'll change all other
architectures, too.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/x86/kernel/mpparse_32.c |6 --
arch/x86/kernel/setup_32.c | 15 ---
arch/
This patch uses the BOOTMEM_EXCLUSIVE, introduced in the previous patch,
to avoid conflicts while reserving the memory for the kdump carpture kernel
(crashkernel=).
The modification has been tested on i386.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/x86/kernel/setu
covered by Vivek Goyal <[EMAIL PROTECTED]>)
3) fix IA64 (didn't compile)
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordom
* Vivek Goyal <[EMAIL PROTECTED]> [2007-10-17 13:05]:
>
>
> I think we should unreserve the chunks of memory we have reserved so
> far (Memory reserved from sidx to i), in case of error.
True. Next version is coming.
Thanks,
Bernhard
-
To unsubscribe from this list: send the line "unsubscri
* Vivek Goyal <[EMAIL PROTECTED]> [2007-10-17 13:05]:
>
> [..]
> > +/*
> > + * If flags is 0, then the return value is always 0 (success). If
> > + * flags contains BOOTMEM_EXCLUSIVE, then -EBUSY is returned if the
> > + * memory already was reserved.
> > + */
> > +extern int reserve_bootmem(unsig
Hi,
* Dave Hansen <[EMAIL PROTECTED]> [2007-10-16 20:08]:
> On Tue, 2007-10-16 at 18:28 +0200, Bernhard Walle wrote:
> >
> > @@ -736,7 +736,7 @@ static int __init smp_scan_config (unsig
> > smp_found_config = 1;
> >
This patch uses the BOOTMEM_EXCLUSIVE, introduced in the previous patch,
to avoid conflicts while reserving the memory for the kdump carpture kernel
(crashkernel=).
The modification has been tested on i386.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/x86/kernel/setu
only for
x86 and breaks other architectures. If the patch is ok, I'll change all other
architectures, too.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/x86/kernel/mpparse_32.c |4 ++--
arch/x86/kernel/setup_32.c | 12 ++--
arch/x86/kernel/setup_64.c |
I'll modify the patch for all
architectures.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
--
-
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-inf
6 and
ia64).
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/ia64/kernel/efi.c | 10 ++
arch/ia64/kernel/setup.c |9 -
arch/x86/kernel/e820_32.c | 18 +-
arch/x86/kernel/e820_64.c |3 ++-
arch/x86/kernel/efi_32.c | 11 ++
* Vivek Goyal <[EMAIL PROTECTED]> [2007-10-16 07:49]:
>
> Shouldn't bootmem allocator have the functionality to flag an error if
> we try to reserve a memory which is already reserved? I see that bootmem
> allocator is currently printing a warning under CONFIG_DEBUG_BOOTMEM.
That's probably bette
* Andi Kleen <[EMAIL PROTECTED]> [2007-10-16 11:59]:
> Vivek Goyal <[EMAIL PROTECTED]> writes:
>
> > Wouldn't it be better if we reserve the code, data and bss memory also
> > using bootmem allocator and when somebody tries to reserve craskernel memory
> > and if there is an overlap, boot memory a
* Andrew Morton <[EMAIL PROTECTED]> [2007-10-15 20:32]:
> On Mon, 15 Oct 2007 13:50:43 +0200
> Bernhard Walle <[EMAIL PROTECTED]> wrote:
>
> > --- a/arch/x86/kernel/e820_32.c
> > +++ b/arch/x86/kernel/e820_32.c
> > @@ -51,6 +51,13 @@ struct re
This patch adds the BSS to the resource tree just as kernel text and kernel
data are in the resource tree. The main reason behind this is to avoid
crashkernel reservation in that area.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/x86/kernel/e820_32.c |8
ar
dump kernel since it checks /proc/iomem. However, the
crashkernel memory would still be reserved.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/x86/kernel/setup_32.c | 31 +--
arch/x86/kernel/setup_64.c | 31 +--
2 fi
n add the BSS resource
and the check for all other architectures that apply.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at h
in parse_crashkernel_mem() by comparing
the return pointer of memparse() with the input pointer and also replaces
all printk(KERN_WARNING msg) with pr_warning(msg).
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
kernel/kexec.c | 54 +++-
* Oleg Verych <[EMAIL PROTECTED]> [2007-09-26 20:18]:
>
> I was thinking about errors in YaST or typos in bootloader config, that
> may appear sometimes. And kernel must tolerate this kind of userspace
> input to be more reliable. But you know better, i just am waving hands.
Of course the kernel
y for i386 and x86_64 as it's done in ia64. Since
both architectures have a relocatable kernel now, that makes perfectly
sense. But that's another patch.
---
This patches improves error handling in parse_crashkernel_mem() by comparing
the return pointer of memparse() with the
long start = 0, end = ULLONG_MAX;
> > + unsigned long long size = -1;
>
> memparse(), as a wrapper for somple_strtoll(), always have a return value
> (zero by default).
> <http://article.gmane.org/gmane.linux.kernel/583426>
Next reply (because of a different
Hi,
* Andrew Morton <[EMAIL PROTECTED]> [2007-09-25 21:45]:
> On Tue, 25 Sep 2007 20:23:02 +0200 Bernhard Walle <[EMAIL PROTECTED]> wrote:
>
> > This patch adapts the ppc64 code to use the generic parse_crashkernel()
> > function introduced in the generic patch
This adds the documentation for the extended crashkernel syntax into
Documentation/kdump/kdump.txt.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
Documentation/kdump/kdump.txt | 26 ++
Documentation/kernel-parameters.txt |7 +++
2 files c
This patch adapts the ppc64 code to use the generic parse_crashkernel()
function introduced in the generic patch of that series.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/powerpc/kernel/machine_kexec.c | 52 ++--
1 file changed, 26 inse
.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
Acked-by: Paul Mundt <[EMAIL PROTECTED]>
---
arch/sh/kernel/machine_kexec.c | 21 -
arch/sh/kernel/setup.c | 38 +-
2 files changed, 33 insertions(+), 26 deletions(-)
-
-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/e820.c |3 +-
arch/x86_64/kernel/machine_kexec.c | 27 -
arch/x86_64/kernel/setup.c | 39 ++---
3 files changed, 34 insertions(+), 35 del
, the crashkernel handling is moved in an own function in
arch/ia64/kernel/setup.c to make the code more readable.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/ia64/kernel/efi.c |4 +-
arch/ia64/kernel/setup.c | 88 +++--
i
-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/i386/kernel/e820.c |3 +-
arch/i386/kernel/machine_kexec.c | 22 -
arch/i386/kernel/setup.c | 49 +++
3 files changed, 46 insertions(+), 28 deletions(-)
Files
parse_crashkernel()
- merge patch that adds documentation do Documentation/kernel-parameters.txt
in documentation patch (this has been an extra patch previously)
- fix build on IA64
- fix build on i386 with CONFIG_NOHIGHMEM
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
--
writes the command line in the configuration then.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
include/linux/kexec.h |2
kernel/kexec.c| 142 ++
2 files changed, 144 insertions(+)
--- a/include/linux/kexec.h
+++ b/inclu
pears in.)
arch/i386/kernel/setup.c:391: error: 'highstart_pfn' undeclared (first use in
this function)
make[1]: *** [arch/i386/kernel/setup.o] Error 1
make: *** [arch/i386/kernel] Error 2
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/i386/kernel/setup.c | 16
* Oleg Verych <[EMAIL PROTECTED]> [2007-09-23 23:15]:
>
> - crashkernel=512M-2G:64M,2G-:[EMAIL PROTECTED]
> + crashkernel=512M-2G,64M,2G-,128M,,offset
> ?
I don't like this syntax.
Thanks,
Bernhard
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a mes
* Oleg Verych <[EMAIL PROTECTED]> [2007-09-23 01:14]:
> * Thu, 20 Sep 2007 19:18:46 +0200
>
> []
> > extern u32 vmcoreinfo_note[VMCOREINFO_NOTE_SIZE/4];
> > extern unsigned int vmcoreinfo_size;
> > extern unsigned int vmcoreinfo_max_size;
> > +int __init parse_crashkernel(char *cmdline, unsigne
Hello,
currently, the parport_pc driver doesn't use IRQs automatically for
PCI devices. However, why is it not possible? It's no problem to find
out the corresponding IRQ, and it should also be possible to use IRQ
sharing. The following patch implements this.
Could somebody tell me what's wrong w
This patch just makes the version number in ips.c and ips.h consistent. It
seems that this has been forgotten in a60768e2d43eb30a1adb8a119aeac35dc0d03ef6.
It also removes code duplication, each number is now only once in the code to
avoid similar errors in the future.
Signed-off-by: Bernhard
This adds the documentation for the extended crashkernel syntax into
Documentation/kernel-parameters.txt.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
Documentation/kernel-parameters.txt |7 +++
1 file changed, 7 insertions(+)
--- a/Documentation/kernel-parameters.txt
This adds the documentation for the extended crashkernel syntax into
Documentation/kernel-parameters.txt.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
Documentation/kernel-parameters.txt |7 +++
1 file changed, 7 insertions(+)
--- a/Documentation/kernel-parameters.txt
* Pavel Machek <[EMAIL PROTECTED]> [2007-09-18 19:21]:
> > This adds the documentation for the extended crashkernel syntax into
> > Documentation/kdump/kdump.txt.
>
> Should you also update kernel-parameters.txt?
Ok, I'll do.
> > +For example:
> > +
> > +crashkernel=512M-2G:64M,2G-:128M
> >
* Andrew Morton <[EMAIL PROTECTED]> [2007-09-20 00:33]:
>
> Could you fix all that up please?
Thanks for the comments -- should be fixed now, see the new patch
series.
Thanks,
Bernhard
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAI
.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
Acked-by: Paul Mundt <[EMAIL PROTECTED]>
---
arch/sh/kernel/machine_kexec.c | 21 -
arch/sh/kernel/setup.c | 38 +-
2 files changed, 33 insertions(+), 26 deletions(-)
-
, the crashkernel handling is moved in an own function in
arch/ia64/kernel/setup.c to make the code more readable.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/ia64/kernel/efi.c |4 +-
arch/ia64/kernel/setup.c | 88 +++--
i
This adds the documentation for the extended crashkernel syntax into
Documentation/kdump/kdump.txt.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
Documentation/kdump/kdump.txt | 26 ++
1 file changed, 26 insertions(+)
--- a/Documentation/kdump/kdump.txt
-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/e820.c |3 +-
arch/x86_64/kernel/machine_kexec.c | 27 -
arch/x86_64/kernel/setup.c | 39 ++---
3 files changed, 34 insertions(+), 35 del
This patch adapts the ppc64 code to use the generic parse_crashkernel()
function introduced in the generic patch of that series.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/powerpc/kernel/machine_kexec.c | 52 ++--
1 file changed, 26 inse
-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/i386/kernel/e820.c |3 ++-
arch/i386/kernel/machine_kexec.c | 22 --
arch/i386/kernel/setup.c | 37 -
3 files changed, 34 insertions(+), 28 deletions(-)
---
writes the command line in the configuration then.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
include/linux/kexec.h |2
kernel/kexec.c| 141 ++
2 files changed, 143 insertions(+)
--- a/include/linux/kexec.h
+++ b/inclu
- print message when no base address is specified on i386/x86_64/sh
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
--
-
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.kern
* Jeremy Fitzhardinge <[EMAIL PROTECTED]> [2007-09-13 23:56]:
>
> > I'd like to know a little bit more about why this is needed, how it will be
> > used, etc. And given that this feature is intended to improve life for
> > distributors, it would be nice to get some feedback from the appropriate
>
This patch adapts the ppc64 code to use the generic parse_crashkernel()
function introduced in the generic patch of that series.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/powerpc/kernel/machine_kexec.c | 52 ++--
1 file changed, 26 inse
, the crashkernel handling is moved in an own function in
arch/ia64/kernel/setup.c to make the code more readable.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/ia64/kernel/efi.c |4 +-
arch/ia64/kernel/setup.c | 88 +++--
i
This adds the documentation for the extended crashkernel syntax into
Documentation/kdump/kdump.txt.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
Documentation/kdump/kdump.txt | 26 ++
1 file changed, 26 insertions(+)
--- a/Documentation/kdump/kdump.txt
.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/sh/kernel/machine_kexec.c | 21 -
arch/sh/kernel/setup.c | 34 +-
2 files changed, 29 insertions(+), 26 deletions(-)
--- a/arch/sh/kernel/machine_kexec.c
+++ b/arch/sh/
-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/e820.c |3 ++-
arch/x86_64/kernel/machine_kexec.c | 27 ---
arch/x86_64/kernel/setup.c | 35 ---
3 files changed, 30 insertions(+), 35 del
writes the command line in the configuration then.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
include/linux/kexec.h |2
kernel/kexec.c| 139 ++
2 files changed, 141 insertions(+)
--- a/include/linux/kexec.h
+++ b/inclu
-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/i386/kernel/e820.c |3 ++-
arch/i386/kernel/machine_kexec.c | 22 --
arch/i386/kernel/setup.c | 33 -
3 files changed, 30 insertions(+), 28 deletions(-)
--- a/arc
change for i386, x86_64, ia64, ppc64 and sh. That
should be all platforms that support kdump in current mainline. I tested all
platforms except sh due to the lack of a sh processor.
The patch series is against 2.6.23-rc4-mm1.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
--
-
To unsub
* Vivek Goyal <[EMAIL PROTECTED]> [2007-09-11 08:09]:
>
> How often does this scenario happen? Anyway, if you run into these issues
> and if it helps, I don't mind additional command line syntax for crashkernel=
Of course, I agree, this is a rare case.
> > This series implements this change for
* Vivek Goyal <[EMAIL PROTECTED]> [2007-09-12 13:23]:
> On Tue, Sep 11, 2007 at 12:01:10PM +0200, Bernhard Walle wrote:
> > * Vivek Goyal <[EMAIL PROTECTED]> [2007-09-11 08:15]:
> > >
> > > "offset" seems to be optional in the new syntax. What
* Lombard, David N <[EMAIL PROTECTED]> [2007-09-11 17:32]:
>
> lilo:
> append=
>
> Appends the options specified to the parameter line passed to
> the kernel.
Given that lilo appends the user-specified command line, I think it's
the best to honor the last value. It has also been the p
* Vivek Goyal <[EMAIL PROTECTED]> [2007-09-11 07:14]:
> On Sun, Sep 09, 2007 at 08:52:58PM +0200, Bernhard Walle wrote:
> > * Yinghai Lu <[EMAIL PROTECTED]> [2007-09-09 19:27]:
> > > >
> > > > +#ifdef CONFIG_KEXEC
> > > ...
> > >
* Vivek Goyal <[EMAIL PROTECTED]> [2007-09-11 08:15]:
>
> "offset" seems to be optional in the new syntax. What happens if user does
> not specify offset. I think crash_base will be set to zero and system will
> try to reserve x amount of memory start at zero? That would fail?
That's handled in t
* Matthew Wilcox <[EMAIL PROTECTED]> [2007-09-09 15:01]:
> On Sun, Sep 09, 2007 at 10:39:18AM +0200, Bernhard Walle wrote:
> > Because the total amount of System RAM must be known when calling this
> > function, efi_memmap_init() is modified to return its comulated
>
&g
* Yinghai Lu <[EMAIL PROTECTED]> [2007-09-09 19:27]:
> >
> > +#ifdef CONFIG_KEXEC
> ...
>
> CONFIG_KEXEC or CONFIG_CRASH_DUMP?
Good question. The crashkernel parameter was CONFIG_KEXEC before, and
I also wondered why, but I didn't change this because maybe there's
some reason I don't know.
Vivek
-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/e820.c |3 ++-
arch/x86_64/kernel/machine_kexec.c | 27 ---
arch/x86_64/kernel/setup.c | 35 ---
3 files changed, 30 insertions(+), 35 del
pointer value. IMO that's better than making the
variable global.
Also, the crashkernel handling is moved in an own function in
arch/ia64/kernel/setup.c to make the code more readable.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/ia64/kernel/efi.c |5 ++
arch/
writes the command line in the configuration then.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
include/linux/kexec.h |2
kernel/kexec.c| 139 ++
2 files changed, 141 insertions(+)
--- a/include/linux/kexec.h
+++ b/inclu
1 - 100 of 243 matches
Mail list logo
