[ Upstream commit bf348f9b78d413e75bb079462751a1d86b6de36c ]
When tag_set->nr_maps is 1, the block layer limits the number of hw queues
by nr_cpu_ids. No matter how many hw queues are used by virtio-blk, as it
has (tag_set->nr_maps == 1), it can use at most nr_cpu_ids hw queues.
In addition,
[ Upstream commit 60ce2858514ed9ccaf00dc7e9f4dc219537e9855 ]
Commit 06a4b6d009a1 ("ARM: 8677/1: boot/compressed: fix decompressor
header layout for v7-M") fixed an issue in the layout of the header
of the compressed kernel image that was caused by the assembler
emitting narrow opcodes for 'mov
From: Andrey Ryabinin
commit f0996bc2978e02d2ea898101462b960f6119b18f upstream.
Building lib/ubsan.c with gcc-9 results in a ton of nasty warnings like
this one:
lib/ubsan.c warning: conflicting types for built-in function
‘__ubsan_handle_negate_overflow’; expected ‘void(void *,
From: Andrew Vasquez
commit 5cbdae10bf11f96e30b4d14de7b08c8b490e903c upstream.
Commit e6f77540c067 ("scsi: qla2xxx: Fix an integer overflow in sysfs
code") incorrectly set 'optrom_region_size' to 'start+size', which can
overflow option-rom boundaries when 'start' is non-zero. Continue setting
[ Upstream commit 88b1a17dfc3ed7728316478fae0f5ad508f50397 ]
This is the same as the traditional 'get_page()' function, but instead
of unconditionally incrementing the reference count of the page, it only
does so if the count was "safe". It returns whether the reference count
was incremented
[ Upstream commit 2ae2c3316fb77dcf64275d011596b60104c45426 ]
The call to of_parse_phandle returns a node pointer with refcount
incremented thus it must be explicitly decremented after the last
usage.
Detected by coccinelle with the following warnings:
On Thu, May 09, 2019 at 11:35:55AM -0700, Yang Shi wrote:
>
>
> On 5/9/19 3:54 AM, Peter Zijlstra wrote:
> > On Thu, May 09, 2019 at 12:38:13PM +0200, Peter Zijlstra wrote:
> >
> > > That's tlb->cleared_p*, and yes agreed. That is, right until some
> > > architecture has level dependent TLBI
On Wed, May 08, 2019 at 11:04:56PM -0700, Christoph Hellwig wrote:
> On Wed, May 08, 2019 at 12:58:32PM -0600, Raul E Rangel wrote:
> > It is possible for queuedata to be cleared in mmc_cleanup_queue before
> > the request has been started.
>
> Errm. I think we need to fix that problem instead
On 5/9/19 3:54 AM, Peter Zijlstra wrote:
On Thu, May 09, 2019 at 12:38:13PM +0200, Peter Zijlstra wrote:
That's tlb->cleared_p*, and yes agreed. That is, right until some
architecture has level dependent TLBI instructions, at which point we'll
need to have them all set instead of cleared.
On Thu, 2019-05-09 at 20:35 +0300, Andy Shevchenko wrote:
> On Thu, May 9, 2019 at 5:18 PM Bjorn Helgaas wrote:
> > Replace dev_printk(KERN_DEBUG) with dev_info() or dev_err() to be more
> > consistent with other logging.
> >
> > These could be converted to dev_dbg(), but that depends on
> >
arch/mips/kernel/perf_event_mipsxx.c: In function 'mipsxx_pmu_enable_event':
arch/mips/kernel/perf_event_mipsxx.c:326:21: error: unused variable 'event'
[-Werror=unused-variable]
struct perf_event *event = container_of(evt, struct perf_event, hw);
^
Fix this by making
On Thu, 9 May 2019 09:51:59 -0700
Linus Torvalds wrote:
> On Thu, May 9, 2019 at 6:01 AM Steven Rostedt wrote:
> >
> > This patch works. Can I get your Signed-off-by for it?
>
> Yes. Please write some kind of comprehensible commit log for it, but
How's this:
"Peter Zijlstra noticed that
On Thu, May 09, 2019 at 01:37:42PM -0400, Steven Rostedt wrote:
> On Thu, May 09, 2019 at 10:14:31AM +0200, Peter Zijlstra wrote:
> >
> > Right; I already fixed that in my patch changing i386's pt_regs.
> >
> > But what I'd love to do is something like the belwo patch, and make all
> > the
On Thu, May 09, 2019 at 05:36:29PM +, Nadav Amit wrote:
> > On May 9, 2019, at 3:38 AM, Peter Zijlstra wrote:
> > diff --git a/mm/mmu_gather.c b/mm/mmu_gather.c
> > index 99740e1dd273..fe768f8d612e 100644
> > --- a/mm/mmu_gather.c
> > +++ b/mm/mmu_gather.c
> > @@ -244,15 +244,20 @@ void
On 5/9/19 3:38 AM, Peter Zijlstra wrote:
On Thu, May 09, 2019 at 09:37:26AM +0100, Will Deacon wrote:
Hi all, [+Peter]
Right, mm/mmu_gather.c has a MAINTAINERS entry; use it.
Sorry for that, I didn't realize we have mmu_gather maintainers. I
should run maintainer.pl.
Also added Nadav
On Wed, May 08, 2019 at 03:57:49PM -0500, Pierre-Louis Bossart wrote:
>
>
> On 5/8/19 11:59 AM, Greg KH wrote:
> > On Wed, May 08, 2019 at 11:42:15AM -0500, Pierre-Louis Bossart wrote:
> > >
> > >
> > > On 5/8/19 4:16 AM, Greg KH wrote:
> > > > On Wed, May 08, 2019 at 01:16:06PM +0530, Vinod
The Chrome OS EC driver attaches to devices using the of_match_table
even when ACPI is the underlying firmware. It does this using the
magic PRP0001 ACPI HID, which tells ACPI to go find an OF compatible
string under the hood and match on that.
The cros_ec_spi driver needs to provide the
On Thu, 9 May 2019 13:02:11 -0500
miny...@acm.org wrote:
> From: Corey Minyard
>
> The function call do_wait_for_common() has a race condition that
> can result in lockups waiting for completions. Adding the thread
> to (and removing the thread from) the wait queue for the completion
> is
From: Cong Wang
cec_timer_fn() is a timer callback which reads ce_arr.array[] and
updates its decay values. However, it runs in interrupt context and the
mutex protection the CEC uses for that array, is inadequate. Convert the
used timer to a workqueue to keep the tasks the CEC performs
From: Borislav Petkov
Hi all,
here are a bunch of fixes and cleanups to the correctable errors
collector which we've been working on in the recent weeks.
Thx.
Borislav Petkov (9):
RAS/CEC: Fix binary search function
RAS/CEC: Fix pfn insertion
RAS/CEC: Check count_threshold
From: Borislav Petkov
Switch to using Donald Knuth's binary search algorithm (The Art of
Computer Programming, vol. 3, section 6.2.1). This should've been done
from the very beginning but the author must've been smoking something
very potent at the time.
The problem with the current one was
From: Borislav Petkov
When the value requested doesn't match the allowed (min,max) range,
the @data buffer should not be modified with the invalid value because
reading "decay_interval" shows it otherwise.
Move the data write after the check.
Signed-off-by: Borislav Petkov
Cc: Tony Luck
Cc:
From: Borislav Petkov
Check the elements order in the array after every insertion.
Signed-off-by: Borislav Petkov
Cc: Tony Luck
Cc: linux-edac
---
drivers/ras/cec.c | 37 +++--
1 file changed, 31 insertions(+), 6 deletions(-)
diff --git a/drivers/ras/cec.c
Thank you.
On Thu, May 9, 2019 at 1:50 AM Catalin Marinas wrote:
>
> Hi,
>
> On Wed, May 08, 2019 at 11:45:03AM -0700, Salman Qazi wrote:
> > What is the intention behind icache_is_aliasing on big.LITTLE systems
> > where some icaches are VIPT and others are PIPT? Is it meant to be
> >
On Thu, May 09, 2019 at 07:41:47PM +0200, Greg KH wrote:
> On Sun, May 05, 2019 at 03:15:53PM +0200, Greg KH wrote:
> > On Fri, May 03, 2019 at 01:45:03PM -0600, Ross Zwisler wrote:
> > > From: Ross Zwisler
> > >
> > > commit 0efa3334d65b7f421ba12382dfa58f6ff5bf83c4 upstream.
> >
> > This
Hi Hans
On 5/9/19 2:50 AM, Hans de Goede wrote:
>
> Hi,
>
> On 09-05-19 06:24, Robert R. Howell wrote:
>> On 4/30/19 8:39 AM, Hans de Goede wrote:
>>>
>>>
>>> I've just tried to reproduce the "Error i2c_dw_xfer call while suspended"
>>> error
>>> on suspend/resume on my own T100TA and I
From: Borislav Petkov
When inserting random PFNs for debugging the CEC through
(debugfs)/ras/cec/pfn, depending on the return value of pfn_set(),
multiple values get inserted per a single write.
That is because simple_attr_write() interprets a retval of 0 as
success and claims the whole input.
From: Borislav Petkov
Free the array page if a failure is encountered while creating the
debugfs nodes.
Signed-off-by: Borislav Petkov
Cc: Tony Luck
Cc: linux-edac
---
drivers/ras/cec.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/ras/cec.c
From: Borislav Petkov
The count_threshold should be checked unconditionally, after insertion
too, so that a count_threshold value of 1 can cause an immediate
offlining. I.e., offline the page on the *first* error encountered.
Add comments to make it clear what cec_add_elem() does, while at it.
Background: Apparently a FreeBSD developer, a viking looking fellow,
has been hiding a secret: just as many of his predecessors in the Danish
cities during WWII (collaborators); He has a disdain for "the jews"
collectively.
(No great surprise: he is a european, and past actions speak louder
From: Borislav Petkov
When dumping the array elements, print them in the following format:
[ PFN | generation in binary | count ]
to be perfectly clear what all those sections are.
Signed-off-by: Borislav Petkov
Cc: Tony Luck
Cc: linux-edac
---
drivers/ras/cec.c | 5 -
1 file
From: Borislav Petkov
... which is the better, more-fitting name anyway.
Tony:
- make action_threshold u64 due to debugfs accessors expecting u64.
- rename the remaining: s/count_threshold/action_threshold/g
Co-developed-by: Tony Luck
Signed-off-by: Tony Luck
Signed-off-by: Borislav Petkov
From: Borislav Petkov
Signed-off-by: Borislav Petkov
---
drivers/ras/cec.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/ras/cec.c b/drivers/ras/cec.c
index c4505c0893a7..5402e907ae7a 100644
--- a/drivers/ras/cec.c
+++ b/drivers/ras/cec.c
@@ -1,4 +1,7 @@
//
From: Tony Luck
The pfn and array files in (debugfs)/ras/cec are intended for debugging
the CEC code itself. They are not needed on production systems, so the
default setting for this CONFIG option is "n".
[ bp: Have it with less ifdeffery by using IS_ENABLED(). ]
Signed-off-by: Tony Luck
пт, 5 апр. 2019 г. в 14:39, Long Li :
>
> From: Long Li
>
> When transport is being destroyed, it's possible that some processes may
> hold memory registrations that need to be deregistred.
>
> Call them first so nobody is using transport resources, and it can be
> destroyed.
>
> Signed-off-by:
On Thu, May 09, 2019 at 04:55:34PM +0200, Borislav Petkov wrote:
> On Fri, May 10, 2019 at 12:52:05AM +1000, Michael Ellerman wrote:
> > Thanks. It would be nice if you could send it as a fix for 5.2, it's the
> > last thing blocking one of my allmodconfig builds. But if you don't
> > think it
From: Corey Minyard
The function call do_wait_for_common() has a race condition that
can result in lockups waiting for completions. Adding the thread
to (and removing the thread from) the wait queue for the completion
is done outside the do loop in that function. However, if the thread
is
On Thu, May 9, 2019 at 8:49 PM Yurii Pavlovskyi
wrote:
> On 08.05.19 15:58, Andy Shevchenko wrote:
> Yes, looking at this patch now I'd guess the refactoring there is really
> misguided as it adds a lot more code than it removes, will drop it
> completely and just add a new condition to the
On Thu, 9 May 2019 13:46:27 -0400
Masayoshi Mizuma wrote:
> From: Masayoshi Mizuma
>
> Cleanup get_grub_index().
Hi Masayoshi,
Thanks for the patches, quick comment below.
>
> Signed-off-by: Masayoshi Mizuma
> ---
> tools/testing/ktest/ktest.pl | 50 +++-
On Thu, May 9, 2019 at 8:29 PM Yurii Pavlovskyi
wrote:
> On 08.05.19 15:36, Andy Shevchenko wrote:> On Fri, Apr 19, 2019 at 1:08 PM
> Yurii Pavlovskyi
> > wrote:
> >> int rv;
> >> + char *wmi_uid;
> >
> > Keep them in reversed spruce order.
>
> What do you mean by that? Do you mean
select_task_rq_* seems to be unchanged. So the search logic to find a cpu
to enqueue when a task becomes runnable is same as before and doesn't do
any kind of cookie matching.
Okay, that's true in task wakeup path, and also load_balance seems to pull task
without checking cookie too. But my
On Thu, May 09, 2019 at 09:53:43AM -0700, Tejun Heo wrote:
> On Tue, May 07, 2019 at 10:01:47AM -0700, Roman Gushchin wrote:
> > In most cases percpu reference counters are not switched to the
> > percpu mode after they reach the atomic mode. Some obvious exceptions
> > are reference counters
On Thu, May 09, 2019 at 04:22:56PM +0200, 'Dmitry Vyukov' via syzkaller wrote:
> > > > > Can the KVM maintainers take a look at this? This doesn't have
> > > > > anything to do
> > > > > with my commit that syzbot bisected it to.
> > > > >
> > > > > +Dmitry, statistics lession: if a crash occurs
(Adding Lorenzo and Sudeep)
On Wed, May 8, 2019 at 8:26 PM Niklas Cassel wrote:
>
> On Wed, May 08, 2019 at 02:48:19AM +0530, Amit Kucheria wrote:
> > On Tue, May 7, 2019 at 1:01 AM Niklas Cassel
> > wrote:
> > >
> > > Add device bindings for CPUs to suspend using PSCI as the enable-method.
>
On Thu, May 9, 2019 at 5:18 PM Bjorn Helgaas wrote:
>
> From: Bjorn Helgaas
>
> This is a collection of updates to Fred's v2 patches from:
>
> https://lore.kernel.org/lkml/20190503035946.23608-1-f...@fredlawl.com
>
> and some follow-on discussion.
>
For non-commented patches,
Reviewed-by:
On 08.05.19 15:58, Andy Shevchenko wrote:
> On Fri, Apr 19, 2019 at 1:12 PM Yurii Pavlovskyi
> wrote:
>
>> - if (value == ASUS_WMI_UNSUPPORTED_METHOD || value &
>> 0xFFF8
>> + if (value == ASUS_WMI_UNSUPPORTED_METHOD || (value &
>> 0xFFF8)
>
> Seems like a
From: Masayoshi Mizuma
Fedora 30 introduces Boot Loader Specification (BLS) [1],
it changes around grub entry configuration.
This patchset deals with the new configuration.
- Add grub2bls option as REBOOT_TYPE to deal with BLS.
- Some cleanup around getting kernel entries.
[1]
From: Masayoshi Mizuma
Update sample.conf for grub2bls.
Signed-off-by: Masayoshi Mizuma
---
tools/testing/ktest/sample.conf | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/tools/testing/ktest/sample.conf b/tools/testing/ktest/sample.conf
index
From: Masayoshi Mizuma
Cleanup get_grub_index().
Signed-off-by: Masayoshi Mizuma
---
tools/testing/ktest/ktest.pl | 50 +++-
1 file changed, 15 insertions(+), 35 deletions(-)
diff --git a/tools/testing/ktest/ktest.pl b/tools/testing/ktest/ktest.pl
index
From: Masayoshi Mizuma
Remove get_grub2_index() because it isn't used anywhere.
Signed-off-by: Masayoshi Mizuma
---
tools/testing/ktest/ktest.pl | 36
1 file changed, 36 deletions(-)
diff --git a/tools/testing/ktest/ktest.pl b/tools/testing/ktest/ktest.pl
From: Masayoshi Mizuma
Fedora 30 introduces Boot Loader Specification (BLS),
it changes around grub entry configuration.
kernel entries aren't in grub.cfg. We can get the entries
by "grubby --info=ALL" command.
Introduce grub2bls as REBOOT_TYPE option for BLS.
Signed-off-by: Masayoshi Mizuma
From: Masayoshi Mizuma
Introduce _get_grub_index() to deal with Boot Loader
Specification (BLS) and cleanup.
Signed-off-by: Masayoshi Mizuma
---
tools/testing/ktest/ktest.pl | 37
1 file changed, 37 insertions(+)
diff --git a/tools/testing/ktest/ktest.pl
On Thu, May 09, 2019 at 06:19:25PM +0200, Sebastian Andrzej Siewior wrote:
> Please:
> - add some RT developers on Cc:
> - add lkml
> - use [PATCH RT] instead just [PATCH] so it is visible that you target
>the RT tree.
Will do. I'll add your diagram below, too.
>
> On 2019-05-08
On Thu, May 09, 2019 at 03:08:16PM +0100, Ben Hutchings wrote:
> This is the start of the stable review cycle for the 3.16.67 release.
> There are 10 patches in this series, which will be posted as responses
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
On Thu, 9 May 2019 07:14:08 +0200, Maxime Chevallier wrote:
> Hello Jakub, David,
>
> On Tue, 7 May 2019 10:28:03 -0700
> Jakub Kicinski wrote:
>
> >> - if (mvpp22_rss_is_supported())
> >> + if (mvpp22_rss_is_supported()) {
> >>dev->hw_features |= NETIF_F_RXHASH;
> >> +
> Hi,
>
> On 5/1/19 4:01 PM, Brendan Higgins wrote:
> > Add documentation for KUnit, the Linux kernel unit testing framework.
> > - Add intro and usage guide for KUnit
> > - Add API reference
> >
> > Signed-off-by: Felix Guo
> > Signed-off-by: Brendan Higgins
> > ---
> > Documentation/index.rst
On Thu, May 09, 2019 at 07:18:28PM +0200, Rafael J. Wysocki wrote:
> So does the patch below fix it for you?
Yes. Thanks for the fix. Feel free to add my tag:
Tested-by: Ido Schimmel
On Thu, May 9, 2019 at 7:00 PM wrote:
> > -Original Message-
> > From: Theodore Ts'o
> >
> > On Thu, May 09, 2019 at 01:52:15PM +0200, Knut Omang wrote:
> > > 1) Tests that exercises typically algorithmic or intricate, complex
> > >code with relatively few outside dependencies, or
On Thu, May 9, 2019 at 5:19 PM Bjorn Helgaas wrote:
> Log messages with pci_dev, not pcie_device. Factor out common message
> prefixes with dev_fmt().
>
> Example output change:
>
> - aer :00:00.0:pci002: AER enabled with IRQ ...
> + pcieport :00:00.0: AER: enabled with IRQ ...
> +
Virtual addresses return from dma(m)_alloc_attrs are opaque in what
backs then, and drivers must not poke into them. Similarly caching
modes are not supposed to be directly set by the driver. Switch the
driver to use the generic DMA API mmap helper to avoid these problems.
Signed-off-by:
On Sun, May 05, 2019 at 03:15:53PM +0200, Greg KH wrote:
> On Fri, May 03, 2019 at 01:45:03PM -0600, Ross Zwisler wrote:
> > From: Ross Zwisler
> >
> > commit 0efa3334d65b7f421ba12382dfa58f6ff5bf83c4 upstream.
>
> This commit id is not in Linus's tree :(
>
Sorry for the noise, I didn't read
On Thu, May 09, 2019 at 10:14:31AM +0200, Peter Zijlstra wrote:
>
> Right; I already fixed that in my patch changing i386's pt_regs.
>
> But what I'd love to do is something like the belwo patch, and make all
> the trampolines (very much including ftrace) use that. Such that we then
> only have
On Thu, May 09, 2019 at 09:31:41AM -0700, Dan Williams wrote:
> diff --git a/drivers/dax/device.c b/drivers/dax/device.c
> index e428468ab661..996d68ff992a 100644
> --- a/drivers/dax/device.c
> +++ b/drivers/dax/device.c
> @@ -184,8 +184,7 @@ static vm_fault_t __dev_dax_pmd_fault(struct dev_dax
>
On Thu, May 09, 2019 at 09:20:06AM -0700, Andy Lutomirski wrote:
> > +END(call_to_exception_trampoline)
> > --- a/arch/x86/kernel/kprobes/core.c
> > +++ b/arch/x86/kernel/kprobes/core.c
> > @@ -731,29 +731,8 @@ asm(
> >".global kretprobe_trampoline\n"
> >".type kretprobe_trampoline,
On Thu, May 9, 2019 at 5:18 PM Bjorn Helgaas wrote:
> Log messages with pci_dev, not pcie_device. Factor out common message
> prefixes with dev_fmt().
>
> Example output change:
>
> - dpc :00:01.1:pcie008: DPC error containment capabilities...
> + pcieport :00:01.1: DPC: error
Virtual addresses return from dma(m)_alloc_coherent are opaque in what
backs then, and drivers must not poke into them. Switch the driver
to use the generic DMA API mmap helper to avoid these problems.
Signed-off-by: Christoph Hellwig
---
drivers/video/fbdev/jz4740_fb.c | 7 ---
1 file
On 08.05.19 15:47, Andy Shevchenko wrote:
> On Fri, Apr 19, 2019 at 1:10 PM Yurii Pavlovskyi
> wrote:
>
> It's rather a big change. Can it be split to smaller pieces?
>
I will then split this into refactoring event code handling in separate
methods and actual event queue support patches.
On Thu, May 9, 2019 at 5:17 PM Bjorn Helgaas wrote:
>
> From: Frederick Lawler
>
> Replace dev_printk(KERN_DEBUG) with dev_info() or dev_err() to be more
> consistent with other logging.
>
> These could be converted to dev_dbg(), but that depends on
> CONFIG_DYNAMIC_DEBUG and DEBUG, and we want
Alex,
On 5/7/19 9:16 AM, Graf, Alexander wrote:
> [CAUTION: External Email]
>
> On 03.05.19 15:37, Suthikulpanit, Suravee wrote:
>> Current logic does not allow VCPU to be loaded onto CPU with
>> APIC ID 255. This should be allowed since the host physical APIC ID
>> field in the AVIC Physical
Hi all,
this series fixes up three mips-specific fbdev drivers to not poke
into the return values from the DMA memory allocators, as those
aren't guranteed to be pages backed (although on mips in practice
they are). Two of them are also fixed up to use the proper DMA API
mmap helper.
Note that
> On May 9, 2019, at 3:38 AM, Peter Zijlstra wrote:
>
> On Thu, May 09, 2019 at 09:37:26AM +0100, Will Deacon wrote:
>> Hi all, [+Peter]
>
> Right, mm/mmu_gather.c has a MAINTAINERS entry; use it.
>
> Also added Nadav and Minchan who've poked at this issue before. And Mel,
> because he loves
Virtual addresses return from dma(m)_alloc_coherent are opaque in what
backs then, and drivers must not poke into them. Switch the driver
to use the generic DMA API mmap helper to avoid these problems.
Signed-off-by: Christoph Hellwig
Acked-by: Bartlomiej Zolnierkiewicz
---
On Tue, May 07, 2019 at 03:16:13PM -0700, Paul E. McKenney wrote:
> On Wed, May 01, 2019 at 01:27:13PM -0700, Paul E. McKenney wrote:
> > On Wed, May 01, 2019 at 03:16:55PM -0400, Steven Rostedt wrote:
> > > On Wed, 1 May 2019 12:12:13 -0700
> > > "Paul E. McKenney" wrote:
> > >
> > >
> > > >
Hello, Linus.
This pull request includes Roman's cgroup2 freezer implementation.
It's a separate machanism from cgroup1 freezer. Instead of blocking
user tasks in arbitrary uninterruptible sleeps, the new implementation
extends jobctl stop - frozen tasks are trapped in jobctl stop until
thawed
On Thu, May 9, 2019 at 5:18 PM Bjorn Helgaas wrote:
> Replace dev_printk(KERN_DEBUG) with dev_info() or dev_err() to be more
> consistent with other logging.
>
> These could be converted to dev_dbg(), but that depends on
> CONFIG_DYNAMIC_DEBUG and DEBUG, and we want most of these messages to
>
Guillaume La Roque writes:
> This property allow drive-strength parameter in uA instead of mA.
>
> Signed-off-by: Guillaume La Roque
> ---
> Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git
Guillaume La Roque writes:
> The purpose of this patchset is to add drive-strength support in meson pinconf
> driver. This is a new feature that was added on the g12a. It is critical for
> us
> to support this since many functions are failing with default pad
> drive-strength.
>
> The value
Hello,
syzbot found the following crash on:
HEAD commit:80f23212 Merge git://git.kernel.org/pub/scm/linux/kernel/g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1630988ca0
kernel config: https://syzkaller.appspot.com/x/.config?x=40a58b399941db7e
Largely mechanical changes: the exported grant table symbols now take
xenhost_t * as a parameter. Also, move the grant table global state
inside xenhost_t.
If there's more than one xenhost, then initialize both.
Signed-off-by: Ankur Arora
---
arch/x86/xen/grant-table.c | 71 +++--
Allow for different hypercall implementations for different xenhost types.
Nested xenhost, which has two underlying xenhosts, can use both
simultaneously.
The hypercall macros (HYPERVISOR_*) implicitly use the default xenhost.x
A new macro (hypervisor_*) takes xenhost_t * as a parameter and does
With nested xenhosts, both the xenhosts could have different supported
xen_features. Add support for probing both.
In addition, validate that features are compatible across xenhosts.
For runtime feature checking, the code uses xen_feature() with the
default xenhost. This should be good enough
Hello, Linus.
Only three commits, of which two are trivial. The non-trivial chagne
is Thomas's patch to switch workqueue from sched RCU to regular one.
The use of sched RCU is mostly historic and doesn't really buy us
anything noticeable.
Thanks.
The following changes since commit
Add xenhost_t which will serve as an abstraction over Xen interfaces.
It co-exists with the PV/HVM/PVH abstractions (x86_init, hypervisor_x86,
pv_ops etc) and is meant to capture mechanisms for communication with
Xen so we could have different types of underlying Xen: regular, local,
and nested.
As part of xenbus init, both frontend, backend interfaces need to talk
on the correct xenbus. This might be a local xenstore (backend) or might
be a XS_PV/XS_HVM interface (frontend) which needs to talk over xenbus
with the remote xenstored. We bootstrap all of these with evtchn/gfn
parameters
HYPERVISOR_shared_info is used for irq/evtchn communication between the
guest and the host. Abstract out the setup/reset in xenhost_t such that
nested configurations can use both xenhosts simultaneously.
In addition to irq/evtchn communication, shared_info is also used for
pvclock and p2m related
Largely mechanical patch that adds a new param, xenhost_t * to the
evtchn interfaces. The evtchn port instead of being domain unique, is
now scoped to xenhost_t.
As part of upcall handling we now look at all the xenhosts and, for
evtchn_2l, the xenhost's shared_info and vcpu_info. Other than this
For configurations with multiple xenhosts, we need to handle events
generated from multiple xenhosts.
Having more than one upcall handler might be quite hairy, and it would
be simpler if the callback from L0-Xen could be bounced via L1-Xen.
This will also mean simpler pv_irq_ops code because now
Abstract out xen_vcpu_id probing via (*probe_vcpu_id)(). Once that is
availab,e the vcpu_info registration happens via the VCPUOP hypercall.
Note that for the nested case, there are two vcpu_ids, and two vcpu_info
areas, one each for the default xenhost and the remote xenhost.
The vcpu_info is
Quoting Taniya Das (2019-05-08 11:24:55)
> Update the init data name for each of the dynamic frequency switch
> controlled clock associated with the RCG clock name, so that it can be
> generated as per the hardware plan. Thus update the macro accordingly.
>
> Signed-off-by: Taniya Das
This
Hi all,
This is an RFC for xenhost support, outlined here by Juergen here:
https://lkml.org/lkml/2019/4/8/67.
The high level idea is to provide an abstraction of the Xen
communication interface, as a xenhost_t.
xenhost_t expose ops for communication between the guest and Xen
(hypercall, cpuid,
On Thu, May 09, 2019 at 10:19:39AM -0700, Kees Cook wrote:
> Hi Greg,
>
> Please pull these lkdtm fixes for next. If possible, it'd be nice to get
> these into v5.2 (they're small fixes), but I'm fine if they have to wait.
> I meant to send these earlier, but got distracted by other things.
Will
xen_cpuid_base() is used to probe and setup features early in a
guest's lifetime.
We want this to behave differently depending on xenhost->type: for
instance, local xenhosts cannot intercept the cpuid instruction at all.
Add op (*cpuid_base)() in xenhost_ops_t.
Signed-off-by: Ankur Arora
---
>From Casey: "There's one bug fix for IPv6 handling and two memory use
improvements."
Plus a couple of further bugfixes.
The following changes since commit fe9fd2ef383c2f5883fcd3f7adce0de9ce2556ff:
Revert "security: inode: fix a missing check for securityfs_create_file"
(2019-04-10 14:59:20
>From Jarkko:
Bugfixes and new selftests for v5.1 features (partial reads in /dev/tpm0).
The following changes since commit 8d93e952fba216cd0811247f6360d97e0465d5fc:
LSM: lsm_hooks.h: fix documentation format (2019-03-26 16:46:22 -0700)
are available in the Git repository at:
Xenhost type xenhost_r0 does not support standard GNTTABOP_map_grant_ref
semantics (map a gref onto a specified host_addr). That's because
since the hypervisor is local (same address space as the caller of
GNTTABOP_map_grant_ref), there is no external entity that could
map an arbitrary page
For the most part, we now pass xenhost_t * as a parameter.
Co-developed-by: Joao Martins
Signed-off-by: Ankur Arora
---
drivers/block/xen-blkback/blkback.c | 34 +
drivers/block/xen-blkback/common.h | 2 +-
drivers/block/xen-blkback/xenbus.c | 63 -
This patch series fixes data hold timing issues for various sdhci-iproc
ip blocks that do not meet the HS50 data hold time. NO_HISPD bit is set
in quirks.
Changes from v2:
- Added info to commit message as to stable tag selection decision
as per Adrian Hunter
Changes from v1:
- Change
Xen ballooning uses hollow struct pages (with the underlying GFNs being
populated/unpopulated via hypercalls) which are used by the grant logic
to map grants from other domains.
This patch allows the default xenhost to provide an alternate ballooning
allocation mechanism. This is expected to be
On 08.05.19 15:36, Andy Shevchenko wrote:> On Fri, Apr 19, 2019 at 1:08 PM
Yurii Pavlovskyi
> wrote:
>> int rv;
>> + char *wmi_uid;
>
> Keep them in reversed spruce order.
What do you mean by that? Do you mean like this?
+ char *wmi_uid;
int rv;
int err;
>> +#define
From: Trac Hoang
The iproc host eMMC/SD controller hold time does not meet the
specification in the HS50 mode. This problem can be mitigated
by disabling the HISPD bit; thus forcing the controller output
data to be driven on the falling clock edges rather than the
rising clock edges.
Stable
501 - 600 of 991 matches
Mail list logo
