On 2020-06-03 14:22, Mike Leach wrote:
Hi Sai,
On Wed, 3 Jun 2020 at 13:14, Sai Prakash Ranjan
wrote:
Hi Mike,
On 2020-06-03 16:57, Mike Leach wrote:
Hi,
On Wed, 3 Jun 2020 at 11:24, Sai Prakash Ranjan
wrote:
Hi Mike,
Thanks again for looking at this.
On 2020-06-03 03:42, Mike Leach
On Tue, Jun 2, 2020 at 8:44 PM Marco Elver wrote:
>
> Adds the portable definitions for __no_sanitize_address, and
> __no_sanitize_undefined, and subsequently changes noinstr to use the
> attributes to disable instrumentation via KASAN or UBSAN.
>
> Link:
On 2020/06/03 21:44, Petr Mladek wrote:
> On Wed 2020-06-03 20:03:28, Tetsuo Handa wrote:
>> On 2020/05/29 22:26, Tetsuo Handa wrote:
>>> By the way, I do worry that people forget to perform these steps when
>>> they do
>>> their tests without asking syzbot...
>>
>> Here is a draft of
On Fri 29-05-20 09:06:08, Feng Tang wrote:
> percpu_counter_sum_positive() will provide more accurate info.
>
> As with percpu_counter_read_positive(), in worst case the deviation
> could be 'batch * nr_cpus', which is totalram_pages/256 for now,
> and will be more when the batch gets enlarged.
>
On Tue, Jun 2, 2020 at 8:44 PM Marco Elver wrote:
>
> Adds config variable CC_HAS_WORKING_NOSANITIZE, which will be true if we
> have a compiler that does not fail builds due to no_sanitize functions.
> This does not yet mean they work as intended, but for automated
> build-tests, this is the
On Wed 03-06-20 17:48:04, Feng Tang wrote:
> On Tue, Jun 02, 2020 at 12:02:22AM -0400, Qian Cai wrote:
> >
> >
> > > On Jun 1, 2020, at 11:37 PM, Feng Tang wrote:
> > >
> > > I re-run the same benchmark with v5.7 and 5.7+remove_warning kernels,
> > > the overall performance change is trivial
On Fri 29-05-20 09:06:10, Feng Tang wrote:
> When checking a performance change for will-it-scale scalability mmap test
> [1], we found very high lock contention for spinlock of percpu counter
> 'vm_committed_as':
>
> 94.14% 0.35% [kernel.kallsyms] [k] _raw_spin_lock_irqsave
>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: d6f9469a03d832dcd17041ed67774ffb5f3e73b3
commit: 6a35ddc5445a8291ced6247a67977e110275acde nfp: tls: implement the stream
sync RX resync
date: 6 months ago
config: arm64-randconfig-r033-20200603 (attached
On Wed, Jun 3, 2020 at 9:52 AM Viresh Kumar wrote:
>
> On 02-06-20, 11:34, Xiongfeng Wang wrote:
> > Hi Viresh,
> >
> > Sorry to disturb you about another problem as follows.
> >
> > CPPC use the increment of Desired Performance counter and Reference
> > Performance
> > counter to get the CPU
On 2020-06-03 13:26, Sai Prakash Ranjan wrote:
Hi Robin,
On 2020-06-03 17:51, Robin Murphy wrote:
On 2020-06-03 13:00, Sai Prakash Ranjan wrote:
Hi Robin, Mathieu
On 2020-06-03 17:07, Robin Murphy wrote:
On 2020-06-01 22:28, Mathieu Poirier wrote:
That being said I'm sure that dependencies
On Wed, Jun 03, 2020 at 01:31:39PM +0200, Michal Vokáč wrote:
> Commit 7e99e3470172 ("net: dsa: remove dsa_switch_alloc helper")
> replaced the dsa_switch_alloc helper by devm_kzalloc in all DSA
> drivers. Unfortunately it introduced a typo in qca8k.c driver and
> wrong argument is passed to the
On Wed, Jun 03, 2020 at 03:41:21PM +0200, Andrew Lunn wrote:
> On Wed, Jun 03, 2020 at 01:31:39PM +0200, Michal Vokáč wrote:
> > Commit 7e99e3470172 ("net: dsa: remove dsa_switch_alloc helper")
> > replaced the dsa_switch_alloc helper by devm_kzalloc in all DSA
> > drivers. Unfortunately it
Hi Mike,
On 2020-06-03 19:04, Robin Murphy wrote:
On 2020-06-03 14:22, Mike Leach wrote:
Hi Sai,
On Wed, 3 Jun 2020 at 13:14, Sai Prakash Ranjan
wrote:
Hi Mike,
On 2020-06-03 16:57, Mike Leach wrote:
Hi,
On Wed, 3 Jun 2020 at 11:24, Sai Prakash Ranjan
wrote:
Hi Mike,
Thanks again
On Wed, Jun 3, 2020 at 7:48 AM Piotr Stankiewicz
wrote:
>
> Seeing as there is shorthand available to use when asking for any type
> of interrupt, or any type of message signalled interrupt, leverage it.
>
> Signed-off-by: Piotr Stankiewicz
> Reviewed-by: Andy Shevchenko
> ---
>
> On Jun 2, 2020, at 1:38 AM, Josh Poimboeuf wrote:
>
> On Sun, May 31, 2020 at 01:26:54PM +0800, changhuaixin wrote:
>> It turned out to be an alignment problem. If sh_size of previous section
>> orc_unwind is not 4-byte aligned, sh_offset of the following orc_lookup
>> section is not
--
OUR GOLDEN OPPORTUNITY
Hello Dear Friend,
Complement of the day, i hope you are doing great today. However, I am
Mrs.Susan Jones, an auditor with one of the new generation banks here
in Burkina Faso.
I am writing you this letter based on the latest development at my
Department. i discovered
The headers_install_all target got removed last year (commit f3c8d4c7a728 and
would someone like to update Documentation/kbuild/headers_install.txt which
still describes it?)
The musl-libc maintainer is using a forked hand-hacked kernel header package in
his toolchain build project
On Wed, 2020-06-03 at 14:47 +0200, Takashi Iwai wrote:
> On Wed, 03 Jun 2020 14:39:24 +0200,
> Macpaul Lin wrote:
> >
> > On Wed, 2020-06-03 at 10:45 +0200, Takashi Iwai wrote:
> > > On Wed, 03 Jun 2020 08:54:51 +0200,
> > > Takashi Iwai wrote:
> > > >
> > > > On Wed, 03 Jun 2020 08:28:09 +0200,
From: Colin Ian King
The variable error is being initialized with a value that is
never read and the -ENOMEM error return is being returned anyhow
by the error exit path to label err_free_mem. The assignment is
redundant and can be removed.
Addresses-Coverity: ("Unused value")
Signed-off-by:
On Wed, Jun 3, 2020 at 8:02 PM Neal Cardwell wrote:
>
> On Wed, Jun 3, 2020 at 1:44 AM Eric Dumazet wrote:
> >
> > On Tue, Jun 2, 2020 at 10:05 PM Jason Xing
> > wrote:
> > >
> > > Hi Eric,
> > >
> > > I'm still trying to understand what you're saying before. Would this
> > > be better as
Hi,
On Wed, 3 Jun 2020 at 14:34, Robin Murphy wrote:
>
> On 2020-06-03 14:22, Mike Leach wrote:
> > Hi Sai,
> >
> > On Wed, 3 Jun 2020 at 13:14, Sai Prakash Ranjan
> > wrote:
> >>
> >> Hi Mike,
> >>
> >> On 2020-06-03 16:57, Mike Leach wrote:
> >>> Hi,
> >>>
> >>> On Wed, 3 Jun 2020 at 11:24,
Hi Robin,
On 2020-06-03 19:10, Robin Murphy wrote:
On 2020-06-03 13:26, Sai Prakash Ranjan wrote:
Hi Robin,
On 2020-06-03 17:51, Robin Murphy wrote:
On 2020-06-03 13:00, Sai Prakash Ranjan wrote:
Hi Robin, Mathieu
On 2020-06-03 17:07, Robin Murphy wrote:
On 2020-06-01 22:28, Mathieu
From: Richard Gong
Patch fixes sparse warnings: using plain integer as NULL pointer. Replaces
equal to with logical not operator.
Reported-by: kbuild test robot
Signed-off-by: Richard Gong
---
drivers/firmware/stratix10-rsu.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
On Tue, Apr 28, 2020 at 05:17:25PM +0200, Joerg Roedel wrote:
> From: Tom Lendacky
>
> Calling down to EFI runtime services can result in the firmware performing
> VMGEXIT calls. The firmware is likely to use the GHCB of the OS (e.g., for
> setting EFI variables), so each GHCB in the system
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: d6f9469a03d832dcd17041ed67774ffb5f3e73b3
commit: 9e00df7156e45e42c695ffc596b4bf1328d00516 crypto: hisilicon - register
zip engine to uacce
date: 3 months ago
config: ia64-randconfig-r026-20200603
On Wed, Jun 3, 2020 at 5:02 AM Neal Cardwell wrote:
>
> On Wed, Jun 3, 2020 at 1:44 AM Eric Dumazet wrote:
> >
> > On Tue, Jun 2, 2020 at 10:05 PM Jason Xing
> > wrote:
> > >
> > > Hi Eric,
> > >
> > > I'm still trying to understand what you're saying before. Would this
> > > be better as
From: Colin Ian King
The variable ret is being initialized with a value that is
never read and it is being updated later with a new value. The
initialization is redundant and can be removed.
Addresses-Coverity: ("Unused value")
Signed-off-by: Colin Ian King
---
drivers/input/mouse/alps.c | 2
Hi Mike,
On 2020-06-03 19:21, Mike Leach wrote:
Hi,
On Wed, 3 Jun 2020 at 14:34, Robin Murphy wrote:
On 2020-06-03 14:22, Mike Leach wrote:
> Hi Sai,
>
> On Wed, 3 Jun 2020 at 13:14, Sai Prakash Ranjan
> wrote:
>>
>> Hi Mike,
>>
>> On 2020-06-03 16:57, Mike Leach wrote:
>>> Hi,
>>>
>>> On
From: Colin Ian King
The variable error is being initialized with a value that is
never read and it is being updated later with a new value. The
initialization is redundant and can be removed.
Addresses-Coverity: ("Unused value")
Signed-off-by: Colin Ian King
---
On Wed, Jun 3, 2020 at 3:49 PM Rob Landley wrote:
>
> The headers_install_all target got removed last year (commit f3c8d4c7a728 and
> would someone like to update Documentation/kbuild/headers_install.txt which
> still describes it?)
>
> The musl-libc maintainer is using a forked hand-hacked
在 2020/6/2 21:14, Josh Poimboeuf 写道:
On Tue, Jun 02, 2020 at 09:22:30AM +0800, Wangshaobo (bobo) wrote:
so i think this question is related to ORC unwinder, could i ask if you have
strategy or plan to avoid this problem ?
I suspect something like this would fix it (untested):
diff --git
On Tue, Jun 2, 2020 at 8:49 PM Nick Desaulniers wrote:
>
> Currently most of our compiler attribute detection is done in
> include/linux/compiler_attributes.h; I think this should be handled
> there. +Miguel Ojeda
Thanks a lot for the CC Nick! Marco is right, since this attribute is
different
* Tomi Valkeinen [200603 12:34]:
> Hi Tony,
>
> On 31/05/2020 22:39, Tony Lindgren wrote:
> > When booting without legacy platform data, we no longer have omap_device
> > calling PM runtime suspend for us on suspend. This causes the driver
> > context not be saved as we have no suspend and
On Wed, Jun 3, 2020 at 9:55 AM Eric Dumazet wrote:
>
> On Wed, Jun 3, 2020 at 5:02 AM Neal Cardwell wrote:
> >
> > On Wed, Jun 3, 2020 at 1:44 AM Eric Dumazet wrote:
> > >
> > > On Tue, Jun 2, 2020 at 10:05 PM Jason Xing
> > > wrote:
> > > >
> > > > Hi Eric,
> > > >
> > > > I'm still trying
In addition, the reason I was testing this was because Linus' master
(d6f9469a03d8 Merge tag 'erofs-for-5.8-rc1' of
git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs) was crashing:
[ 5.368948] loop: module loaded
[ 5.372113] Unable to handle kernel paging request at virtual address
On Wed, Jun 03, 2020 at 02:51:02PM +0100, Colin King wrote:
> From: Colin Ian King
>
> The variable error is being initialized with a value that is
> never read and the -ENOMEM error return is being returned anyhow
> by the error exit path to label err_free_mem. The assignment is
> redundant
From: SeongJae Park
DAMON's main idea is not limited to virtual address space. To prepare
for further expansion of the support for other address spaces including
physical memory, this commit modifies one of its core struct, 'struct
damon_region' to use virtual memory independent address space
From: Colin Ian King
Currently when the call to fsp_reg_write fails -EIO is not being returned
because the count is being returned instead of the return value in retval.
Fix this by returning the value in retval instead of count.
Addresses-Coverity: ("Unused value")
Fixes: fc69f4a6af49 ("Input:
When lookup the symbols of module by module_kallsyms_lookup_name(),
the symbols address is visible only if the module's status isn't
MODULE_STATE_UNFORMED, This is problematic.
When complete_formation is done, the state of the module is modified
to MODULE_STATE_COMING, and the symbol of module is
From: SeongJae Park
Currently, DAMON[1] supports only virtual memory address spaces because it
utilizes PTE Accessed bits as its low-level access check primitive and ``struct
vma`` as a way to address the monitoring target regions. However, the core
idea of DAMON, which makes it able to provide
From: SeongJae Park
Some users would want to monitor only a part of the entire virtual
memory address space. The '->init_target_regions' callback is therefore
provided, but only programming interface can use it.
For the reason, this commit introduces a new debugfs file,
'init_region'. Users
From: SeongJae Park
This commit allows DAMON users to configure their own monitoring target
regions initializer / updater. Using this, users can confine the
monitoring address spaces as they want. For example, users can track
only stack, heap, shared memory area, or specific file-backed area,
From: SeongJae Park
There are unnecessarily duplicated code in DAMON, that can be eliminated
by using the new struct, 'damon_addr_range'. This commit cleans up the
DAMON code in the way.
Signed-off-by: SeongJae Park
---
mm/damon-test.h | 36 ++--
mm/damon.c
From: SeongJae Park
This commit documents the 'initial_regions' feature.
Signed-off-by: SeongJae Park
---
Documentation/admin-guide/mm/damon/usage.rst | 34
1 file changed, 34 insertions(+)
diff --git a/Documentation/admin-guide/mm/damon/usage.rst
Add entry for ARM Intelligent Power Allocation - thermal governor.
Signed-off-by: Lukasz Luba
---
Hi Daniel,
Could you pick it up, please?
Regards,
Lukasz
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index e64e5db31497..8ce4677477a4 100644
From: SeongJae Park
DAMON assumes the target region is in virtual address space and
therefore uses PTE Accessed bit checking for access checking. However,
as some CPU provides H/W based memory access check features that usually
more accurate and light-weight than PTE Accessed bit checking, some
On Wed, Jun 03, 2020 at 08:40:24PM +1200, Barry Song wrote:
> if users give a name saved in stack, the current code will generate magic
> pointer.
> if users don't give a name(NULL), kasprintf() will always return NULL as
> we are at the early stage. that means cma_init_reserved_mem() will return
On Wed, Jun 3, 2020 at 3:51 PM Rob Landley wrote:
> um
> gcc: error: missing argument to ‘-Wframe-larger-than=’
> Makefile:1230: *** Headers not exportable for the um architecture. Stop.
> make: *** [__build_one_by_one] Error 2
Exporting headers of UML makes not much sense.
--
Thanks,
On Wed, Jun 03, 2020 at 08:40:25PM +1200, Barry Song wrote:
> once we enable CMA_DEBUGFS, we will get the below errors:
> directory 'cma-hugetlb' with parent 'cma' already present
>
> only the first numa node will get a directory in debugfs.
> we should have different names for different CMA
From: SeongJae Park
This commit implements the four callbacks (->init_target_regions,
->update_target_regions, ->prepare_access_check, and ->check_accesses)
for the basic access monitoring of the physical memory address space.
By setting the callback pointers to point those, users can easily
Thu, May 28, 2020 at 05:12:40PM CEST, vadym.koc...@plvision.eu wrote:
[...]
>+}
>+
>+int prestera_hw_port_info_get(const struct prestera_port *port,
>+u16 *fp_id, u32 *hw_id, u32 *dev_id)
Please unify the ordering of "hw_id" and "dev_id" with the rest of the
From: SeongJae Park
This commit adds description for the physical memory monitoring usage in
the DAMON document.
Signed-off-by: SeongJae Park
---
Documentation/admin-guide/mm/damon/usage.rst | 42 ++--
1 file changed, 29 insertions(+), 13 deletions(-)
diff --git
From: SeongJae Park
This commit makes the debugfs interface to support the physical memory
monitoring, in addition to the virtual memory monitoring.
Users can do the physical memory monitoring by writing a special
keyword, 'paddr\n' to the 'pids' debugfs file. Then, DAMON will check
the
On 03/06/2020 15:09, Dan Carpenter wrote:
> On Wed, Jun 03, 2020 at 02:51:02PM +0100, Colin King wrote:
>> From: Colin Ian King
>>
>> The variable error is being initialized with a value that is
>> never read and the -ENOMEM error return is being returned anyhow
>> by the error exit path to label
A deadlock caused by logbuf_lock occurs when panic:
a) Panic CPU is running in non-NMI context
b) Panic CPU sends out shutdown IPI via NMI vector
c) One of the CPUs that we bring down via NMI vector holded logbuf_lock
d) Panic CPU try to hold logbuf_lock, then
On Sat, May 16, 2020 at 09:57:14AM +0200, Borislav Petkov wrote:
> Just a reminder so that this doesn't get lost:
>
> On Tue, Apr 28, 2020 at 05:16:35PM +0200, Joerg Roedel wrote:
> > + if (exit_info_1 & IOIO_TYPE_STR) {
> > + int df = (regs->flags & X86_EFLAGS_DF) ? -1 : 1;
>
> ...
On Sun, May 31, 2020 at 8:26 PM Giovanni Gherdovich wrote:
>
> The product mcnt * arch_max_freq_ratio can overflows u64.
>
> For context, a large value for arch_max_freq_ratio would be 5000,
> corresponding to a turbo_freq/base_freq ratio of 5 (normally it's more like
> 1500-2000). A large
Hi Jean,
On Tue, May 19, 2020 at 11:20:55PM -0700, Sean Christopherson wrote:
> On Tue, Apr 28, 2020 at 05:16:35PM +0200, Joerg Roedel wrote:
> > + /*
> > +* For the string variants with rep prefix the amount of in/out
> > +* operations per #VC exception is
On Sun, May 31, 2020 at 8:26 PM Giovanni Gherdovich wrote:
>
> There may be CPUs that support turbo boost but don't declare any turbo
> ratio, i.e. their MSR_TURBO_RATIO_LIMIT is all zeroes. In that condition
> scale-invariant calculations can't be performed.
>
> Signed-off-by: Giovanni
Hi Piotr,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on pci/next]
[also build test ERROR on mkp-scsi/for-next scsi/for-next linus/master v5.7
next-20200603]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we
> Its time cost is about 800 nanoseconds on a 2C/4T platform and
> 2~3 microseconds on a 2S/36C/72T server in normal case, and in
> worst case where vm_committed_as's spinlock is under severe
> contention, it costs 30~40 microseconds for the 2S/36C/72T sever,
This will be likely 40-80us on larger
Thu, May 28, 2020 at 05:12:40PM CEST, vadym.koc...@plvision.eu wrote:
[...]
>+static int prestera_port_create(struct prestera_switch *sw, u32 id)
>+{
>+ struct prestera_port *port;
>+ struct net_device *dev;
>+ int err;
>+
>+ dev = alloc_etherdev(sizeof(*port));
>+ if
In order to edit orc_lookup table via sorttable, type of section
orc_lookup needs to be SHT_PROGBITS instead of SHT_NOBITS.
Linker script doesn't seem to allow manual specification of the section
type, so just write a byte into the section instead.
Signed-off-by: Josh Poimboeuf
Signed-off-by:
Since orc tables are already sorted by sorttable tool, let us move
building of fast lookup table into sorttable tool too. This saves us
6380us from boot time under Intel(R) Xeon(R) CPU E5-2682 v4 @ 2.50GHz
with 64 cores.
Signed-off-by: Huaixin Chang
Signed-off-by: Shile Zhang
---
Move building of fast lookup table from boot to sorttable tool. This saves us
6380us boot time on Intel(R) Xeon(R) CPU E5-2682 v4 @ 2.50GHz with cores.
Changelog v2:
1. Type of section orc_lookup needs to be SHT_PROGBITS.
2. unwind_init() cannot be removed totally as setting lookup_num_blocks is
The orc fast lookup table is built by scripts/sorttable tool. All that
is left is setting lookup_num_blocks.
Signed-off-by: Huaixin Chang
Signed-off-by: Shile Zhang
---
arch/x86/kernel/unwind_orc.c | 40
1 file changed, 40 deletions(-)
diff --git
On Wed, 3 Jun 2020 08:51:13 +0900
Masami Hiramatsu wrote:
> On Tue, 2 Jun 2020 09:21:45 -0400
> Steven Rostedt wrote:
>
> > On Tue, 2 Jun 2020 18:08:31 +0900
> > Masami Hiramatsu wrote:
> >
> > > +++ b/tools/testing/selftests/ftrace/test.d/template
> > > @@ -1,6 +1,7 @@
> > > #!/bin/sh
>
On Mon, 29 Apr 2019 18:16:51 +0200
"Maciej S. Szmigiero" wrote:
> This series adds support for analog part of Medion 95700 in the cxusb
> driver.
>
> What works:
> * Video capture at various sizes with sequential fields,
> * Input switching (TV Tuner, Composite, S-Video),
> * TV and radio
On Wed, May 20, 2020 at 05:51:27AM -0700, Eric Dumazet wrote:
>
> On 5/19/20 11:42 PM, Ahmed S. Darwish wrote:
> > Hello Eric,
> >
> > On Tue, May 19, 2020 at 07:01:38PM -0700, Eric Dumazet wrote:
> >>
> >> On 5/19/20 2:45 PM, Ahmed S. Darwish wrote:
> >>> Sequence counters write paths are
Hello Sumit,
if this doc is for driver developers it might be useful to add some
code examples how to register drivers on tee bus.
Best regards,
Maxim.
On Wed, 3 Jun 2020 at 14:31, Sumit Garg wrote:
>
> Update documentation with TEE bus infrastructure which provides an
> interface for kernel
Wed, Jun 03, 2020 at 04:29:44PM CEST, j...@resnulli.us wrote:
>Thu, May 28, 2020 at 05:12:40PM CEST, vadym.koc...@plvision.eu wrote:
>
>[...]
>
>>+static int prestera_port_create(struct prestera_switch *sw, u32 id)
>>+{
>>+ struct prestera_port *port;
>>+ struct net_device *dev;
>>+
Hi Chuhong,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on v5.7 next-20200603]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base
Thu, May 28, 2020 at 05:12:42PM CEST, vadym.koc...@plvision.eu wrote:
>Add very basic support for devlink interface:
>
>- driver name
>- fw version
>- devlink ports
>
>Signed-off-by: Vadym Kochan
>---
> drivers/net/ethernet/marvell/prestera/Kconfig | 1 +
>
In order to edit orc_lookup table via sorttable, type of section
orc_lookup needs to be SHT_PROGBITS instead of SHT_NOBITS.
Linker script doesn't seem to allow manual specification of the section
type, so just write a byte into the section instead.
Signed-off-by: Josh Poimboeuf
Signed-off-by:
Since orc tables are already sorted by sorttable tool, let us move
building of fast lookup table into sorttable tool too. This saves us
6380us from boot time under Intel(R) Xeon(R) CPU E5-2682 v4 @ 2.50GHz
with 64 cores.
Signed-off-by: Huaixin Chang
Signed-off-by: Shile Zhang
---
Move building of fast lookup table from boot to sorttable tool. This saves us
6380us boot time on Intel(R) Xeon(R) CPU E5-2682 v4 @ 2.50GHz with cores. It
adds a little more than 7ms to boot time when testing on the same CPU.
Changelog v3:
1. Modify annotation of unwind_init().
Changelog v2:
1.
The orc fast lookup table is built by scripts/sorttable tool. All that
is left is setting lookup_num_blocks.
Signed-off-by: Huaixin Chang
Signed-off-by: Shile Zhang
---
arch/x86/kernel/unwind_orc.c | 41 ++---
1 file changed, 2 insertions(+), 39 deletions(-)
On Wed, Jun 03, 2020 at 12:34:35PM +0800, Hillf Danton wrote:
>
> On Tue, 2 Jun 2020 17:55:17 -0400 "J. Bruce Fields" wrote:
> >
> > As far as I know, this one's still unresolved. I can't see the bug from
> > code inspection, and we don't have a reproducer. If anyone else sees
> > this or has
On Wed, Jun 03, 2020 at 03:18:46PM +0100, Colin Ian King wrote:
> On 03/06/2020 15:09, Dan Carpenter wrote:
> > On Wed, Jun 03, 2020 at 02:51:02PM +0100, Colin King wrote:
> >> From: Colin Ian King
> >>
> >> The variable error is being initialized with a value that is
> >> never read and the
On Wed, 3 Jun 2020 at 15:32, Marco Elver wrote:
>
> On Wed, 3 Jun 2020 at 14:18, Peter Zijlstra wrote:
> >
> > On Wed, Jun 03, 2020 at 02:08:57PM +0200, Marco Elver wrote:
> >
> > > What is the .config you used? I somehow can't reproduce. I've applied
> > > the patches on top of -tip/master.
> >
On Wed, Jun 03, 2020 at 03:32:57PM +0200, Joerg Roedel wrote:
> On Wed, Jun 03, 2020 at 04:20:57PM +0530, Abdul Haleem wrote:
> > @Joerg, Could you please have a look?
>
> Can you please try the attached patch?
Hi Joerg,
I did hit the similar boot failue on a Power9 baremetal box(mentioned in
Hi Jonathan,
something I forgot, about the __packed attribute for the sensor data structure
struct inv_icm42600_fifo_sensor_data located inside inv_icm42600_buffer.h.
I added it because this structure is used for decoding the FIFO data frame
which can be unaligned. It is also used for storing
Add shutdown/wakeup a resource eemi operations to shutdown
or bringup a resource.
Signed-off-by: Ben Levinsky
---
v3:
- add xilinx-related platform mgmt fn's instead of wrapping around
function pointer in xilinx eemi ops struct
- fix formatting
v4:
- add default values for enums
---
The u64_stats mechanism uses sequence counters to protect against 64-bit
values tearing on 32-bit architectures. Updating such statistics is a
sequence counter write side critical section.
Preemption must be disabled before entering this seqcount write critical
section. Failing to do so, the
R5 is included in Xilinx Zynq UltraScale MPSoC so by adding this
remotproc driver, we can boot the R5 sub-system in different
configurations.
Acked-by: Stefano Stabellini
Acked-by: Ben Levinsky
Reviewed-by: Radhey Shyam Pandey
Signed-off-by: Ben Levinsky
Signed-off-by: Wendy Liang
Hi,
Since patch #7 and #8 from the series:
[PATCH v1 00/25] seqlock: Extend seqcount API with associated locks
https://lore.kernel.org/lkml/20200519214547.352050-1-a.darw...@linutronix.de
are now pending on the lockdep/x86 IRQ state tracking patch series:
[PATCH 00/14] x86/entry:
Commit bf7afb29d545 ("phy: improve safety of fixed-phy MII register
reading") protected the fixed PHY status with a sequence counter.
Two years later, commit d2b977939b18 ("net: phy: fixed-phy: remove
fixed_phy_update_state()") removed the sequence counter's write side
critical section --
For optimized block readers not holding a mutex, the "number of sectors"
64-bit value is protected from tearing on 32-bit architectures by a
sequence counter.
Disable preemption before entering that sequence counter's write side
critical section. Otherwise, the read side can preempt the write
Commit 3c3b177a9369 ("reservation: add support for read-only access
using rcu") introduced a sequence counter to manage updates to
reservations. Back then, the reservation object initializer
reservation_object_init() was always inlined.
Having the sequence counter initialization inlined meant
The u64_stats mechanism uses sequence counters to protect against 64-bit
values tearing on 32-bit architectures. Updating u64_stats is thus a
sequence counter write side critical section where preemption must be
disabled.
For mdiobus_stats_acct(), disable preemption upon the u64_stats update.
It
Provide basic driver to control Arm R5 co-processor found on
Xilinx ZynqMP UltraScale+ and Versal MPSoC's.
Currently it is able to start, stop and load elf on to the
processor.
The driver was tested on Xilinx ZynqMP and Versal.
v2:
- remove domain struct as per review from Mathieu
v3:
- add
This patch adds APIs to provide access and a configuration interface
to the current power state of a sub-system on Zynqmp sub-system.
Signed-off-by: Ben Levinsky
---
v3:
- add xilinx-related platform mgmt fn's instead of wrapping around
function pointer in xilinx eemi ops struct
v4:
- add
Sequence counters write paths are critical sections that must never be
preempted, and blocking, even for CONFIG_PREEMPTION=n, is not allowed.
Commit 5dbe7c178d3f ("net: fix kernel deadlock with interface rename and
netdev name retrieval.") handled a deadlock, observed with
CONFIG_PREEMPTION=n,
Add binding for ZynqMP R5 OpenAMP.
Represent the RPU domain resources in one device node. Each RPU
processor is a subnode of the top RPU domain node.
Signed-off-by: Ben Levinsky
Signed-off-by: Jason Wu
Signed-off-by: Wendy Liang
Signed-off-by: Michal Simek
---
v3:
- update zynqmp_r5 yaml
On Sun, May 31, 2020 at 8:26 PM Giovanni Gherdovich wrote:
>
> Be defensive against the case where the processor reports a base_freq
> larger than turbo_freq (the ratio would be zero).
>
> Signed-off-by: Giovanni Gherdovich
> Signed-off-by: Peter Zijlstra (Intel)
> Fixes: 1567c3e3467c ("x86,
Add ZynqMP firmware ioctl enums for RPU configuration.
Signed-off-by: Ben Levinsky
---
v3:
- add xilinx-related platform mgmt fn's instead of wrapping around
function pointer in xilinx eemi ops struct
v4:
- add default values for enums
---
include/linux/firmware/xlnx-zynqmp.h | 19
Please pull the proc-linus branch from the git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
proc-linus
HEAD: 9d78edeaec759f997c303f286ecd39daee166f2a proc: proc_pid_ns takes
super_block as an argument
This branch has 4 sets of changes:
proc:
TEST REPORT: BROKEN PATCH
Thanks to everyone for working on the fixed link feature of lan743x eth driver.
I received more test hardware today, and one piece of hardware (EVBlan7430)
becomes incompatible by the patch. We need to roll back for now. Sorry.
I’ll discuss about options of how to
On Wed, Jun 03, 2020 at 06:03:17AM -0700, Rajat Jain wrote:
> Currently, an external malicious PCI device can masquerade the VID:PID
> of faulty gfx devices, and thus apply iommu quirks to effectively
> disable the IOMMU restrictions for itself.
>
> Thus we need to ensure that the device we are
Something went wrong, don't mind it
On 03/06/2020 16:29, Pavel Begunkov wrote:
> The first one adds checks {SQPOLL,IOPOLL}. IOPOLL check can be
> moved in the common path later, or rethinked entirely, e.g.
> not io_iopoll_req_issued()'ed for unsupported opcodes.
>
> 3 others are just cleanups on
501 - 600 of 1155 matches
Mail list logo
