Since the transition to hrtimers there is no more need to set a minimum
RX timeout to work around latency issues.
Signed-off-by: Ulrich Hecht
---
drivers/tty/serial/sh-sci.c | 13 +
1 file changed, 1 insertion(+), 12 deletions(-)
diff --git a/drivers/tty/serial/sh-sci.c b/drivers
o or what defines t == 0?
...
Regards,
Ulrich Windl
08 64228/102328 134935
Regards,
Ulrich
Hi!
Thanks for the patch. Verified it against data sheet, the magic numbers check
out.
Reviewed-by: Ulrich Hecht
CU
Uli
> On 09/17/2020 9:59 PM Lad Prabhakar
> wrote:
>
>
> Add pins, groups and functions for the VIN1-B [data/sync/field/clkenb/clk]
> and VIN2-G8.
>
res;
get_res(&res);
printf("resolution is 0.%09ld\n", res.tv_nsec);
return(result);
}
- it is intentional that the program aborts on error
Output from a newer machine:
get_res: resolution is 0.1
get_res: smallest delta is 0.00030
get_res: largest delta is 0.00050
resolution is 0.00030
Regards,
Ulrich Windl
(Keep me on CC if I should read your replies)
), '#7=.sirq' (software
IRQs), '#8=.st' (stolen)
Is "idle" the only field that is in USER_HZ? If so it makes it hard to be used
by a univarsal utility like my monitoring plugin that can read _any_ value from
procfs.
For reference, here's the consistency check
On Fri, 29 May 2020 13:27:35 +0200
Daniel Kiper wrote:
> Below you can find my rough idea of the bootloader log format which is
> generic thing but initially will be used for TrenchBoot work. I
> discussed this proposal with Ross and Daniel S. So, the idea went
> through initial sanitization. Now
expected by our freeze code, in particular in gup the
existing reference is simply the one from the pte. So in this case our
freeze *would* succeeed.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU/Linux compilers and toolchain
ulrich.weig...@de.ibm.com
On Tue, May 05, 2020 at 05:34:45AM -0700, Dave Hansen wrote:
> On 5/4/20 6:41 AM, Ulrich Weigand wrote:
> > You're right that there is no mechanism to prevent new references,
> > but that's really never been the goal either. We're simply trying
> > to ensur
27;t think Linux mm code would be able to handle the
case where a file-backed page is in the page table but not page cache).
I'm not sure what exactly the requirements for your use case are; if those
are significantly differently, maybe we can work together to find an
approach that works for both?
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU/Linux compilers and toolchain
ulrich.weig...@de.ibm.com
rtual/net/lo/name_assign_type: Invalid argument
/sys/devices/virtual/net/lo/speed
Found in 4.12.14-95.6-default of SLES SP4 (x86_64)
Regards,
Ulrich
;i2c: mediatek: disable zero-length transfers for
> mt8183")
> Signed-off-by: Fabien Parent
Thank you! Tested successfully on Acer R13 Chromebook (mt8173).
Tested-by: Ulrich Hecht
CU
Uli
ret = of_thermal_get_ntrips(tsc->zone);
> if (ret < 0)
> --
> 2.17.1
>
Reviewed-by: Ulrich Hecht
CU
Uli
TTR(rx_fifo_trigger, 0644, rx_trigger_show, rx_trigger_store);
> +static DEVICE_ATTR_RW(rx_fifo_trigger);
>
> static ssize_t rx_fifo_timeout_show(struct device *dev,
> struct device_attribute *attr,
> --
> 2.17.1
>
Reviewed-by: Ulrich Hecht
CU
Uli
-git a/drivers/gpu/drm/rcar-du/rcar_du_regs.h
> b/drivers/gpu/drm/rcar-du/rcar_du_regs.h
> index bc87f080b170..fb9964949368 100644
> --- a/drivers/gpu/drm/rcar-du/rcar_du_regs.h
> +++ b/drivers/gpu/drm/rcar-du/rcar_du_regs.h
> @@ -197,6 +197,11 @@
> #define DEFR6_MLOS1 (1 << 2)
> #define DEFR6_DEFAULT(DEFR6_CODE | DEFR6_TCNE1)
>
> +#define DEFR70x000ec
> +#define DEFR7_CODE (0x7779 << 16)
> +#define DEFR7_CMME1 BIT(6)
> +#define DEFR7_CMME0 BIT(4)
> +
Reviewed-by: Ulrich Hecht
CU
Uli
signed variables to int, adding one to srr, and
> using a single DIV_ROUND_CLOSEST().
>
> Fixes: 63ba1e00f178a448 ("serial: sh-sci: Support for HSCIF RX sampling point
> adjustment")
> Signed-off-by: Geert Uytterhoeven
Reviewed-by: Ulrich Hecht
CU
Uli
offer a TAI-based time, or,
maybe even better: The kernel could run on TAI internally, and convert to UNIX
time scale as needed.
I'll leave exact specification and implementation to the really clever guys.
Regards,
Ulrich
P.S. Not subscribed to the kernel-list so if you want to talk to me keep me on
CC: preferably
>>>>> On Mon, 11 Feb 2019, Ulrich Mueller wrote:
>>>>> On Mon, 11 Feb 2019, Domenico Andreoli wrote:
>> On Mon, Feb 11, 2019 at 12:08:32AM +0100, Kristian Fiskerstrand wrote:
>>> It was [pointed out] by one of our license group that [hash.h] is the
&g
/history.git/commit/?id=882ad449046cec136c484dd2b3659fb4c683e0a3
filemap.c has a copyright line by Linus, but git blame shows that
the relevant code was added in 2002 with a commit by Rik van Riel:
https://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git/commit/?id=e5191c50d12621e04f8bc247dcb6a0f4ad76ae26
The relevant thread in LKML is here:
https://lkml.org/lkml/2002/2/18/1970
Ulrich
s/tty/serial/sh-sci.c
> @@ -1872,6 +1872,7 @@ static int sci_request_irq(struct sci_port *port)
> }
>
> desc = sci_irq_desc + i;
> + port->irqstr[j] = NULL;
> if (SCIx_TEIDRI_IRQ_EXISTS(port)) {
> /*
> * ERI and BRI are muxed, just register ERI and
> --
> 2.17.1
>
Reviewed-by: Ulrich Hecht
CU
Uli
bri->set_sda = set_sda_gpio_value;
> + bri->set_sda = set_sda_gpio_value;
> }
> return;
> }
> --
> 2.11.0
>
Reviewed-by: Ulrich Hecht
CU
Uli
On Mon, Jul 31, 2017 at 6:28 PM, Peter Rosin wrote:
> On 2017-07-31 18:00, Greg Kroah-Hartman wrote:
>> On Mon, Jul 31, 2017 at 12:04:35PM +0200, Peter Rosin wrote:
>>> From: Ulrich Hecht
>>>
>>> Required for __must_check.
>>>
>>> Signe
7;s random). It's unlikely, but it can happen. The question is whether the
probability of non-unique values from /dev/urandom is any higher than that for
values read from /dev/random. One _might_ be able to predict the values from
/dev/urandom.
Regards,
Ulrich
>
> Jeff
>
&
initialized and working. Such
> devices
> commonly start working after the the root partition is mounted as it
> contains
> all drivers, all configuration information etc.
>
> Note, during the development of my /dev/random implementation, I added the
> getrandom-like b
I'm sorry for using that address as sender in my previous message; it was an
oversight! The CC: address was correct, however. You can drop above address
from your replies.
Hi folks,
maybe someone has a idea on this:
https://bugzilla.opensuse.org/show_bug.cgi?id=1032832
Regards,
Ulrich
i: implement FIFO threshold register setting")
>>
>> Forgot to add a call to this new function?
>
> I think this is fixed by a patch I just took into my tree, which isn't
> in linux-next yet. Right Ulrich?
That is correct, it's called in "[PATCH v4 2/4] serial: sh-sci:
SCIFA/B RX FIFO software timeout".
CU
Uli
83809.595235] [<7fb04560dba0>] 0x7fb04560db9f
>>> Ulrich Windl schrieb am 07.12.2016 um 13:23 in Nachricht <5847FF5E.7E4 :
>>> 161 :
60728>:
> Hi again!
>
> An addition: Processes doing such I/O seem to be unkillable, and I also
> cannot change the queue paramete
nonvoluntary_ctxt_switches: 1
Best regards,
Ulrich
>>> Ulrich Windl schrieb am 07.12.2016 um 13:19 in Nachricht <5847FE66.7E4 :
>>> 161 :
60728>:
> Hi again!
>
> Maybe someone can confirm this:
> If you have a device (e.g. multipath map) that limits max_sectors_kb to
&
nyway).
Last seen with this kernel (SLES11 SP4 on x86_64): Linux version
3.0.101-88-default (geeko@buildhost) (gcc version 4.3.4 [gcc-4_3-branch
revision 152973] (SUSE Linux) ) #1 SMP Fri Nov 4 22:07:35 UTC 2016 (b45f205)
Regards,
Ulrich
>>> Ulrich Windl schrieb am 23.08.2016 um 17:0
>>> Mark D Rustad schrieb am 31.08.2016 um 17:32 in
>>> Nachricht
:
> Ulrich Windl wrote:
>
>> So without partition the throughput is about twice as high! Why?
>
> My first thought is that by starting at block 0 the accesses were aligned
> with
at 0x7fe18823e000: 0.038380s
time to close /dev/disk/by-id/dm-name-FirstTest-32_part2: 0.265687s
So the correctly aligned partition is two to three times faster than the badly
aligned partition (write-only case), and it's about the performance of an
unpartitioned disk.
Regards,
Ulrich
>&
: 0.069956s
time to close /dev/disk/by-id/dm-name-FirstTest-32: 0.327232s
So without partition the throughput is about twice as high! Why?
Regards
Ulrich
(253:8)
FirstTest-32(253:7)
# cat /sys/block/dm-8/queue/max_sectors_kb
1024
After "# echo 128 >/sys/block/dm-8/queue/max_sectors_kb" things still did not
get better.
Can't blk_rq_check_limits() do anything more clever than returning -EIO?
Regards,
Ulrich
P.S: Keep me in CC:, please!
I came across a problem with code which uses a cpuset CG and tries to
be responsible and clean up after itself. The code attached at the
bottom illustrates the problem. It's only long because it has no
dependencies aside from the basic runtime and should work on all
machines. You need to run it
false positives' as the repeated cancel/restart
of watchdog_timer_fn() prevents the 'watchdog/N' thread from running
(i.e. I think the thread is not prevented from running by something
actually hogging CPU N).
Regards,
Uli
- Original Message -
From: "Josh Hunt&quo
#x27;s patch and it
did not help. After that I did a git bisect to figure out when the soft
lockup was fixed and it appears to be resolved after one of the commits
in this series:
commit 81a4beef91ba4a9e8ad6054ca9933dff7e25ff28
Author: Ulrich Obergfell
Date: Fri Sep 4 15:45:15 2015 -0700
watchdog: introduce watchd
t; is needed to
get the fix permanently into Linux.
My proposal many years ago was to use ADJ_* style flags only for the Linux
specialities (the adjtime() part of adjtimex()), and use the MOD_* style flags
for the NTP part of adjtimex().
Regards,
Ulrich
---
Appendix: Linux has only these:
/*
==
My proposal to improve sysctl documentation is obvious, and no, I don't mean
"Use the source, Luke!" ;-)
(I'm not subscribed to LKML)
Regards,
Ulrich
Tejun,
> Sure, separating the knobs out isn't difficult. I still don't like
> the idea of having multiple set of similar knobs controlling about the
> same thing tho.
>
> For example, let's say there's a user who boots with "nosoftlockup"
> explicitly. I'm pretty sure the user wouldn't be inten
mind is: Would the workqueue watchdog
participate in the lockup detector suspend/resume mechanism, and if yes, how
would it be integrated into this ?
Regards,
Uli
- Original Message -
From: "Tejun Heo"
To: "Don Zickus"
Cc: "Ulrich Obergfell" , "Ing
suspended, and the thread could thus
interfere unexpectedly with the code that requested to suspend the
lockup detector. Avoid the race by calling
get_online_cpus() in lockup_detector_suspend()
put_online_cpus() in lockup_detector_resume()
Signed-off-by: Ulrich Obergfell
---
kernel/watchdog.c
This patch set addresses various races in relation to CPU hotplug
and a race in relation to watchdog timer expiry. I discovered the
corner cases during code inspection. I haven't seen any of these
issues occur in practice.
Ulrich Obergfell (4):
watchdog: avoid race between lockup det
ix this by checking the current value of 'watchdog_thresh'.
Signed-off-by: Ulrich Obergfell
---
kernel/watchdog.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/watchdog.c b/kernel/watchdog.c
index 84c4744..18f34cf 100644
--- a/kernel/watchdog.c
+++ b/kernel/watchdo
get|put}_online_cpus() in proc_watchdog_common()
{get|put}_online_cpus() in proc_watchdog_thresh()
{get|put}_online_cpus() in proc_watchdog_cpumask()
Signed-off-by: Ulrich Obergfell
---
kernel/watchdog.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/kernel/watchdog.c b/ker
watchdog_{park|unpark}_threads() are now called in code paths that
protect themselves against CPU hotplug, so {get|put}_online_cpus()
calls are redundant and can be removed.
Signed-off-by: Ulrich Obergfell
---
kernel/watchdog.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions
Commit-ID: 26c21dd9885a2d8a4f4d539917c4877ffd399286
Gitweb: http://git.kernel.org/tip/26c21dd9885a2d8a4f4d539917c4877ffd399286
Author: Ulrich Hecht
AuthorDate: Wed, 30 Sep 2015 12:03:07 +0200
Committer: Thomas Gleixner
CommitDate: Wed, 30 Sep 2015 21:02:22 +0200
irqchip/renesas-intc
ke error returns from kthread_park()
in order to test the patches.
Regards,
Uli
- Original Message -
From: "Andrew Morton"
To: "Ulrich Obergfell"
Cc: linux-kernel@vger.kernel.org, dzic...@redhat.com, atom...@redhat.com
Sent: Wednesday, September 30, 2015 1:30:36 AM
Sub
It makes sense to place watchdog_{dis|enable}_all_cpus() outside of
the ifdef so that _both_ are available even if CONFIG_SYSCTL is not
defined.
Signed-off-by: Ulrich Obergfell
---
kernel/watchdog.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/kernel/watchdog.c b
update_watchdog_all_cpus() now passes errors from watchdog_park_threads()
up to functions in the call chain. This allows watchdog_enable_all_cpus()
and proc_watchdog_update() to handle such errors too.
Signed-off-by: Ulrich Obergfell
---
kernel/watchdog.c | 30 +++---
1
Restore the previous value of watchdog_thresh _and_ sample_period
if proc_watchdog_update() returns an error. The variables must be
consistent to avoid false positives of the lockup detectors.
Signed-off-by: Ulrich Obergfell
---
kernel/watchdog.c | 7 ---
1 file changed, 4 insertions(+), 3
the lockup detectors will soon be disabled by the callers anyway.
Signed-off-by: Ulrich Obergfell
---
kernel/watchdog.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/kernel/watchdog.c b/kernel/watchdog.c
index 3bc22a9..af70bf2 100644
--- a/kernel/watchdog.c
++
lockup_detector_suspend() now handles errors from watchdog_park_threads().
Signed-off-by: Ulrich Obergfell
---
kernel/watchdog.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/kernel/watchdog.c b/kernel/watchdog.c
index 457113c..3bc22a9 100644
--- a/kernel/watchdog.c
+++ b/kernel
s. Failure becomes visible to the
user as follows:
- error messages from lockup_detector_suspend()
or watchdog_enable_all_cpus()
- the state that can be read from /proc/sys/kernel/watchdog_enabled
- the 'write' system call in the latter call chain returns an error
Signed-off-by: Ulrich Obergfell
---
arch/x86/kernel/cpu/perf_event_intel.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/cpu/perf_event_intel.c
b/arch/x86/kernel/cpu/perf_event_intel.c
index 0357bf7..abb25c3 100644
--- a/arch/x86/kernel/cpu
l=linux-kernel&m=143869949229461&w=2
Ulrich Obergfell (2):
watchdog: rename watchdog_suspend() and watchdog_resume()
watchdog: use pr_debug() in fixup_ht_bug() failure path
arch/x86/kernel/cpu/perf_event_intel.c | 6 +++---
include/linux/nmi.h| 8 +++
watchdog_suspended variables and their relationship.
Signed-off-by: Ulrich Obergfell
---
arch/x86/kernel/cpu/perf_event_intel.c | 4 ++--
include/linux/nmi.h| 8
kernel/watchdog.c | 26 ++
3 files changed, 28 insertions(+), 10
> - Original Message -
> From: "Andrew Morton"
> ...
> On Sat, 1 Aug 2015 14:49:23 +0200 Ulrich Obergfell
> wrote:
>
>> This interface can be utilized to deactivate the hard and soft lockup
>> detector temporarily. Callers are expected to
> - Original Message -
> From: "Michal Hocko"
...
> On Sat 01-08-15 14:49:22, Ulrich Obergfell wrote:
>> These functions are intended to be used only from inside kernel/watchdog.c
>> to park/unpark all watchdog threads that are specified in watchdog_cpuma
> - Original Message -
> From: "Don Zickus"
...
> On Tue, Aug 04, 2015 at 03:31:30PM +0200, Michal Hocko wrote:
>> On Sat 01-08-15 14:49:25, Ulrich Obergfell wrote:
>> [...]
>> > @@ -3368,7 +3368,10 @@ static __init int fix
Peter,
>> I posted the patch set here:
>>
>> https://lkml.org/lkml/2015/8/1/64
>> https://lkml.org/lkml/2015/8/1/65
>> https://lkml.org/lkml/2015/8/1/66
>> https://lkml.org/lkml/2015/8/1/67
>> https://lkml.org/lkml/2015/8/1/68
>
> If only you didn't use lkml.org links, that site is fla
> - Original Message -
> From: "Guenter Roeck"
> ...
> Subject: Re: [PATCH 2/4] watchdog: introduce watchdog_suspend() and
> watchdog_resume()
>
> On Sat, Aug 01, 2015 at 02:49:23PM +0200, Ulrich Obergfell wrote:
>> This interface can be utilized t
Don,
> Uli privately has been working on a patchset that cleans up a bunch of these
> race conditions. We believe it should cover this case. It uses the
> proc_mutex to synchronize everything.
>
> I think he is reaching out to you. If you could try his patchset to see if
> it fixes things, it
This interface can be utilized to deactivate the hard and soft lockup
detector temporarily. Callers are expected to minimize the duration of
deactivation. Multiple deactivations are allowed to occur in parallel
but should be rare in practice.
Signed-off-by: Ulrich Obergfell
---
include/linux
Remove update_watchdog() and restart_watchdog_hrtimer() since these
functions are no longer needed. Changes of parameters such as the
sample period are honored at the time when the watchdog threads are
being unparked.
Signed-off-by: Ulrich Obergfell
---
kernel/watchdog.c | 40
Remove watchdog_nmi_disable_all() and watchdog_nmi_enable_all()
since these functions are no longer needed. If a subsystem has a
need to deactivate the watchdog temporarily, it should utilize the
watchdog_suspend() and watchdog_resume() functions.
Signed-off-by: Ulrich Obergfell
---
arch/x86
These functions are intended to be used only from inside kernel/watchdog.c
to park/unpark all watchdog threads that are specified in watchdog_cpumask.
Signed-off-by: Ulrich Obergfell
---
kernel/watchdog.c | 36
1 file changed, 36 insertions(+)
diff --git a
pected that the duration of deactivation will be short.
Ulrich Obergfell (4):
watchdog: introduce watchdog_park_threads() and
watchdog_unpark_threads()
watchdog: introduce watchdog_suspend() and watchdog_resume()
watchdog: use park/unpark functions in update_watchdog_all_cpus()
w
READ? (i.e. #define IOPRIO_WHO_PROCESS
IOPRIO_WHO_THREAD /* and #define IOPRIO_WHO_THREAD */)
Regards,
Ulrich
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
Frederic,
since you changed the function name, you may want to adjust the comment header
too .
v
/**
* smpboot_register_percpu_thread - Register a per_cpu thread related to
hotplug
* @plug_thread:Hotplug thread descriptor
+ * @cpumask:
>>> Martin Steigerwald schrieb am 02.07.2015 um 11:26 in
Nachricht <1479160.a5Vb4cJSSF@merkaba>:
> On Thursday 02 July 2015 10:50:13 Ulrich Windl wrote:
>> Hi!
>
> Hi Ulrich,
>
>> I'm not subscribed, so plese CC: me for your replies.
>>
&g
ll of "uptime" seems to confirm my suspect:
windl> uptime
10:41am up 23 days 18:49, 1 user, load average: 0.08, 0.05, 0.05
windl> uptime
10:48am up 23 days 18:56, 1 user, load average: 0.00, 0.04, 0.05
windl> cat /proc/loadavg
0.00 0.04 0.05 1/108 9704
I'll attach a sample graph.
Regards,
Ulrich
t (%-16s%8lu kB\n) in a constant
also, allowing a change at one point to affect every item...
Probably gcc will optimize the code anyway, so there won't be much difference
regarding performance.
Regards,
Ulrich Windl
--
To unsubscribe from this list: send the line "unsubscribe li
(on and off TM)
> - Implemented support for EBB register set
> - Implemented review comments on previous versions
> - Some code re-arrangements, re-writes and documentation
> - Added comprehensive list of test cases into selftests
This addresses all the issues I raised in my comments on V7.
The regi
Peter,
please see my comments in-line.
Regards,
Uli
- Original Message -
From: "Peter Zijlstra"
To: "Michal Hocko"
[...]
> On Mon, May 18, 2015 at 11:03:37AM +0200, Michal Hocko wrote:
>> This doesn't hang anymore. I've just had to move the mutex definition
>> up to make it compile.
reproduce.
>> > >
>> > > So've tried to bisect ^80dcc31fbe55 e4b0db72be24 and merged 80dcc31fbe55
>> > > in each step.
>> >
>> > Good extra work! Thanks.
>> >
>> > > This lead to:
>> > >
>> > >
- Original Message -
From: "Chris Metcalf"
[...]
On 04/21/2015 08:32 AM, Ulrich Obergfell wrote:
>> Chris,
>>
>> in v9, smpboot_update_cpumask_percpu_thread() allocates 'tmp' mask
>> dynamically.
>> This allocation can fail and thus
- Original Message -
From: "Chris Metcalf"
[...]
> On 04/22/2015 04:20 AM, Ulrich Obergfell wrote:
>> Chris,
>>
>> in principle the change looks o.k. to me, even though I'm not really familiar
>> with the watchdog_nmi_disable_all() and watchd
- Original Message -
From: "Don Zickus"
[...]
> On Tue, Apr 21, 2015 at 10:07:00AM -0400, Ulrich Obergfell wrote:
>>
>> Chris,
>>
[...]
>> I think the user should only be allowed to specify a mask that is a subset of
>> tick_nohz_full_mask as o
> - Original Message -
> From: "Andrew Morton"
> To: "Don Zickus"
> Cc: "LKML" , "Ulrich Obergfell"
>
> Sent: Wednesday, April 22, 2015 10:12:01 PM
> Subject: Re: [PATCH] watchdog: Fix watchdog_nmi_enable_all()
>
> On W
Chris,
in https://lkml.org/lkml/2015/4/17/616 you stated:
">> + alloc_cpumask_var(&watchdog_cpumask_for_smpboot, GFP_KERNEL);
>
> alloc_cpumask_var could fail?
Good catch; if I get a failure I'll just return early without trying to
start the watchdog, since clearly things are too memo
or_init() is executed before fixup_ht_bug().
Regards,
Uli
On 04/16/2015 06:46 AM, Ulrich Obergfell wrote:
> if a user changes watchdog parameters in /proc/sys/kernel, the watchdog
> threads
> are not stopped and restarted in all cases. Parameters can also be changed 'on
> the fl
sible inside EBB)
So I'm not really familiar with the EBB stuff. But just as a
general note, if those are in fact related (i.e. on every machine
that has EBB, all those registers will be available), it might
indeed make more sense to collect them into a single note section
(NT_PPC_EBB?) after
Chris,
I think it would also be nice to check the plausibility of the user input.
+int proc_watchdog_cpumask(struct ctl_table *table, int write,
+ void __user *buffer, size_t *lenp, loff_t *ppos)
+{
+int err;
+
+mutex_lock(&watchdog_proc_mutex);
+
ker" , "Don Zickus"
, "Ingo Molnar" , "Andrew Morton"
, "Andrew Jones" , "chai wen"
, "Ulrich Obergfell" , "Fabian
Frederick" , "Aaron Tomlin" , "Ben Zhang"
, "Christoph Lameter" , "Gilad Ben-Yos
Anshuman Khandual wrote on 13.04.2015
10:48:57:
> On 04/10/2015 04:03 PM, Ulrich Weigand wrote:
> > - You provide checkpointed FPR and VMX registers, but there doesn't
seem
> > to be any way to get at the checkpointed *VSX* registers (i.e. the
part
> > that is nei
to determine
whether the NMI watchdog is running, not the content of watchdog_user_enabled.
The attached [RFC PATCH 1/1] has undergone minimal testing only.
Ulrich Obergfell (1):
watchdog: fix watchdog_nmi_enable_all()
kernel/watchdog.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion
ABLED bit
in 'watchdog_enabled'.
Signed-off-by: Ulrich Obergfell
---
kernel/watchdog.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/watchdog.c b/kernel/watchdog.c
index 2316f50..cba2110 100644
--- a/kernel/watchdog.c
+++ b/kernel/watchdog.c
@@ -608,7 +60
Chris,
if a user changes watchdog parameters in /proc/sys/kernel, the watchdog threads
are not stopped and restarted in all cases. Parameters can also be changed 'on
the fly', for example like 'watchdog_thresh' in the following flow of execution:
proc_watchdog_thresh
proc_watchdog_update
also provide
the opportunity to operate on the full 64-bit register set. Both
apply independently of whether the target process is 32-bit or
64-bit.
Is this not correct?
Bye,
Ulrich
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a m
hwell"
To: "Andrew Morton" , "Chris Metcalf"
Cc: linux-n...@vger.kernel.org, linux-kernel@vger.kernel.org, "Ulrich
Obergfell" , "Don Zickus"
Sent: Tuesday, April 7, 2015 1:21:53 PM
Subject: linux-next: manual merge of the akpm-current tree with the
Chris,
I'd like to comment on the following proposed change:
+int proc_dowatchdog_exclude(struct ctl_table *table, int write,
+void __user *buffer, size_t *lenp, loff_t *ppos)
+{
+int err;
+
+mutex_lock(&watchdog_proc_mutex);
+err = proc_do_lar
ince
> > we're now in nontransactional state, and there is probably no way
> > to force us back into transactional/suspended state ...).
>
> Yep.
So right now I'd tend to prefer (A)+(A'), but the important thing is
that the kernel seems to provide all features required for GDB to
implement any of the above, so we can still make that decision later.
> Getting back to the kernel interface, are you happy with what Anshuman
> has proposed in the current series?
Given the discussion above, this seems fine to me now.
Bye,
Ulrich
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
{
vbd_free(&be->blkif->vbd);
xenbus_dev_fatal(dev, err, "creating sysfs entries");
}
break;
}
Itself vbd_create() does not log a message, and neither does
blkdev_get_by_dev() where the err
ers, issues the trechkpt
instruction to move them to the checkpointed register, and then loads
the normal register set, before returning to user space? Then it does
indeed appear that both sets *are* modifyable, and thus the kernel
interface should export them as such.
Bye,
Ulrich
--
To unsubsc
splay current position (already reflecting
the fact that the transaction will abort), and use it when changing
register values e.g. to effect an inferior function call
- a new ptrace register set should allow access (read-only) to the
*running* register values
-- GDB can use this to display
m9g-multiplatform. Without this, Ethernet
>> doesn't work, as the ZB clock is disabled by clk_disable_unused().
>> Testing on r8a73a4/ape6evm-multiplatform would be appreciated.
>
> Has anyone tried this on r8a73a4/ape6evm-multiplatform?
Works like a charm.
Tested-by: Ulrich H
r a section ".reg-s390-system-call", but that would be
somewhat confusing. Using a new, platform-specific note type for ARM64
would appear to fit better with existing precedent.
Bye,
Ulrich
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the bo
the erro message if possible.
Regards,
Ulrich Windl
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
can find the details there. I thought the
problem is important enough to let you know...
Regards,
Ulrich
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo
1 - 100 of 623 matches
Mail list logo
