Changelog since v1
o Drop single-pass patch
(vincent)
o Scope variables used for SIS_AVG_CPU
(dietmar)
o Remove redundant assignment (dietmar
This reduces the amount of
Andrew, Jakub,
On Sat, Dec 5, 2020 at 10:28 AM Sven Van Asbroeck wrote:
>
> From: Sven Van Asbroeck
>
> On the ksz8795, if the devicetree contains a cpu node,
> devicetree parsing fails and the whole driver errors out.
>
> Fix the devicetree parsing code by making it use the
> correct number of
On Tue, Dec 08, 2020 at 03:33:24PM +0100, Peter Zijlstra wrote:
> On Tue, Dec 08, 2020 at 06:31:12PM +0800, Boqun Feng wrote:
> > These tests are added for two purposes:
> >
> > * Test the implementation of wait context checks and related
> > annotations.
> >
> > * Semi-document the
Hi,
On 12/8/20 1:28 PM, Zou Wei wrote:
> Fix the following sparse warnings:
>
> drivers/platform/x86/intel_speed_select_if/isst_if_mmio.c:23:24: warning:
> symbol 'mmio_range_devid_0' was not declared. Should it be static?
> drivers/platform/x86/intel_speed_select_if/isst_if_mmio.c:28:24:
The passive file in sysfs forces the usage of a passive trip point set
by the userspace when a broken BIOS does not provide the mitigation
temperature for such thermal zone. The hardware evolved a lot since
2008 as a good thermal management is no longer an option.
Linux on the other side also
On 12/8/20 5:07 AM, Peter Zijlstra wrote:
On Fri, Nov 20, 2020 at 11:14:16PM -0500, Waiman Long wrote:
@@ -1032,40 +901,16 @@ rwsem_down_read_slowpath(struct rw_semaphore *sem, int
state, long count)
*
* We can take the read lock directly without doing
*
On Tue, 2020-12-08 at 16:27 +0100, Hans de Goede wrote:
> Hi,
>
> On 12/8/20 4:22 PM, Pandruvada, Srinivas wrote:
> > On Tue, 2020-12-08 at 20:28 +0800, Zou Wei wrote:
> > > Fix the following sparse warnings:
> > >
> > > drivers/platform/x86/intel_speed_select_if/isst_if_mmio.c:23:24:
> > >
Hi all,
This patch series documents best practices for COMPILE_TEST and
architecture/platform dependencies, like already in use in most
subsystems, to serve as a point of reference.
Thanks for your comments!
Geert Uytterhoeven (2):
Documentation/kbuild: Document COMPILE_TEST
Document best practises for using COMPILE_TEST dependencies.
Signed-off-by: Geert Uytterhoeven
---
Documentation/kbuild/kconfig-language.rst | 11 +++
1 file changed, 11 insertions(+)
diff --git a/Documentation/kbuild/kconfig-language.rst
b/Documentation/kbuild/kconfig-language.rst
Document best practises for using architecture and platform dependencies.
Signed-off-by: Geert Uytterhoeven
---
Documentation/kbuild/kconfig-language.rst | 24 +++
1 file changed, 24 insertions(+)
diff --git a/Documentation/kbuild/kconfig-language.rst
Hi,
On 12/8/20 4:22 PM, Pandruvada, Srinivas wrote:
> On Tue, 2020-12-08 at 20:28 +0800, Zou Wei wrote:
>> Fix the following sparse warnings:
>>
>> drivers/platform/x86/intel_speed_select_if/isst_if_mmio.c:23:24:
>> warning: symbol 'mmio_range_devid_0' was not declared. Should it be
>> static?
>>
On Tue, Dec 08, 2020 at 09:46:18AM +0530, Anshuman Khandual wrote:
> This overrides arch_get_mappabble_range() on s390 platform which will be
> used with recently added generic framework. It drops a redundant similar
> check in vmem_add_mapping() while compensating __segment_load() with a new
>
Schönen Tag
Ich bin Anthony Calder, Anwalt aus Togo. Ich habe Sie bezüglich des
Nachlasses des verstorbenen Dr. Edwin-Fonds in Höhe von 8,5 Millionen
US-Dollar kontaktiert, der auf Ihr Konto zurückgeführt werden soll.
Darüber hinaus möchte ich, dass Sie bei dieser Transaktion vertraulich
On Tue, 2020-12-08 at 20:28 +0800, Zou Wei wrote:
> Fix the following sparse warnings:
>
> drivers/platform/x86/intel_speed_select_if/isst_if_mmio.c:23:24:
> warning: symbol 'mmio_range_devid_0' was not declared. Should it be
> static?
>
On Tue, Dec 08, 2020 at 08:18:21PM +0530, Sameer Pujar wrote:
> > I don't seem to have them in my backlog so either there was feedback
> > from someone else I was expecting to see addressed or some other issue.
> I am pretty sure that it is not because of any outstanding comments, because
> I
On Mon, 07 Dec 2020 15:27:55 +0100, Michael Klein wrote:
> Add devicetree binding documentation for regulator-poweroff driver.
>
> Signed-off-by: Michael Klein
> ---
> .../power/reset/regulator-poweroff.yaml | 53 +++
> 1 file changed, 53 insertions(+)
> create mode
On Sat, 05 Dec 2020 18:24:17 +0300, Serge Semin wrote:
> DWC USB3 DT node is supposed to be compliant with the Generic xHCI
> Controller schema, but with additional vendor-specific properties, the
> controller-specific reference clocks and PHYs. So let's convert the
> currently available legacy
Le 05/12/2020 à 20:17, Rasmus Villemoes a écrit :
The translation from the ucc_geth_num_of_threads enum value to the
actual count can be written somewhat more compactly with a small
lookup table, allowing us to replace the four switch statements.
Signed-off-by: Rasmus Villemoes
---
On 08/12/2020 15:37, Lukasz Luba wrote:
>
>
> On 12/8/20 1:51 PM, Daniel Lezcano wrote:
>>
>> Hi Lukasz,
>>
>> On 08/12/2020 10:36, Lukasz Luba wrote:
>>> Hi Daniel,
>>
>> [ ... ]
>>
static void thermal_zone_device_init(struct thermal_zone_device
*tz)
@@ -553,11 +555,9 @@
On Tue, 8 Dec 2020 at 16:12, Mel Gorman wrote:
>
> On Tue, Dec 08, 2020 at 03:47:40PM +0100, Vincent Guittot wrote:
> > > I considered it but made the choice to exclude the cost of cpumask_and()
> > > from the avg_scan_cost instead. It's minor but when doing the original
> >
> > At the cost of a
On Tue, Dec 08, 2020 at 05:57:07PM +0900, Joonsoo Kim wrote:
> On Mon, Dec 07, 2020 at 09:25:54AM -0800, Paul E. McKenney wrote:
> > On Mon, Dec 07, 2020 at 06:02:53PM +0900, Joonsoo Kim wrote:
> > > Hello, Paul.
> > >
> > > On Fri, Dec 04, 2020 at 04:40:52PM -0800, paul...@kernel.org wrote:
> >
Le 05/12/2020 à 20:17, Rasmus Villemoes a écrit :
These macros both have the value 32, there's no point first
initializing align to a lower value.
If anything, one could throw in a
BUILD_BUG_ON(UCC_GETH_TX_BD_RING_ALIGNMENT < 4), but it's not worth it
- lots of code depends on named
On Tue, Dec 08, 2020 at 03:47:40PM +0100, Vincent Guittot wrote:
> > I considered it but made the choice to exclude the cost of cpumask_and()
> > from the avg_scan_cost instead. It's minor but when doing the original
>
> At the cost of a less readable code
>
Slightly less readable, yes.
> >
Le 05/12/2020 à 20:17, Rasmus Villemoes a écrit :
struct ucc_geth_info is somewhat large, and on systems with only one
or two UCC instances, that just wastes a few KB of memory. So
allocate and populate a chunk of memory at probe time instead of
initializing them all during driver init.
Note
Hi Peter,
Thanks for the comments.
On 2020/12/8 22:16, Peter Zijlstra wrote:
> On Tue, Dec 08, 2020 at 09:49:57AM +0800, Aubrey Li wrote:
>> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
>> index c4da7e17b906..b8af602dea79 100644
>> --- a/kernel/sched/core.c
>> +++ b/kernel/sched/core.c
From: Zhang Xiaohui
mwifiex_config_scan() calls memcpy() without checking
the destination size may trigger a buffer overflower,
which a local user could use to cause denial of service
or the execution of arbitrary code.
Fix it by putting the length check before calling memcpy().
Signed-off-by:
On 08-12-20, 15:50, Peter Zijlstra wrote:
> On Tue, Dec 08, 2020 at 09:46:54AM +0530, Viresh Kumar wrote:
> > Viresh Kumar (3):
> > sched/core: Move schedutil_cpu_util() to core.c
> > sched/core: Rename schedutil_cpu_util() and allow rest of the kernel
> > to use it
> > thermal:
Le 08/12/2020 à 15:52, Aneesh Kumar K.V a écrit :
Christophe Leroy writes:
search_exception_tables() is an heavy operation, we have to avoid it.
When KUAP is selected, we'll know the fault has been blocked by KUAP.
Otherwise, it behaves just as if the address was already in the TLBs
and no
On Tue, Nov 03, 2020 at 10:45:54AM +0100, Arnd Bergmann wrote:
> I had it there originally, I guess I should have left it there ;-)
>
> When I changed it, I was considering to do the same for additional
> syscalls that have very small differences now (timer_create,
> rt_sigqueueinfo,
On Tue, Dec 08, 2020 at 09:50:49AM +0100, Sebastian Andrzej Siewior wrote:
> On 2020-12-07 08:06:48 [-0800], Paul E. McKenney wrote:
> > > Yes, but it triggers frequently. Like `rcuc' is somehow is aligned with
> > > the timeout.
> >
> > Given that a lot of RCU processing is event-driven based on
Hi Jarkko,
On Fri, 2020-12-04 at 17:30 +0200, Jarkko Sakkinen wrote:
> On Wed, Dec 02, 2020 at 02:34:07PM -0500, gmail Elaine Palmer wrote:
> > Hi Sumit,
> >
> > Thank you for the detailed descriptions and examples of trust sources
> > for Trusted Keys. A group of us in IBM (Stefan Berger,
On Tue, Dec 08, 2020 at 09:11:29AM +0100, Peter Zijlstra wrote:
> On Mon, Dec 07, 2020 at 11:44:06AM -0800, Paul E. McKenney wrote:
>
> > Also, in this particular case, why data_race() rather than READ_ONCE()?
> > Do we really expect the compiler to be able to optimize this case
> > significantly
Hi Hans,
On 12/7/20 11:21 AM, Hans Verkuil wrote:
> On 07/12/2020 10:06, Stanimir Varbanov wrote:
>>
>>
>> On 12/2/20 1:12 PM, Hans Verkuil wrote:
>>> On 24/11/2020 00:02, Stanimir Varbanov wrote:
Add Content light level and Mastering display colour volume v4l2
compounf controls,
Create CLL and Mastering display colour volume v4l2 controls for
encoder, add handling of HDR10 PQ SEI packet payloads for v4.
Signed-off-by: Stanimir Varbanov
---
drivers/media/platform/qcom/venus/core.h | 3 ++
drivers/media/platform/qcom/venus/hfi_cmds.c | 8 +
Document Content light level and Mastering display colour volume.
Signed-off-by: Stanimir Varbanov
---
.../userspace-api/media/v4l/common.rst| 1 +
.../media/v4l/ext-ctrls-colorimetry.rst | 88 +++
2 files changed, 89 insertions(+)
create mode 100644
On Tue, 8 Dec 2020 21:16:04 +0800
Ran Wang wrote:
> Signed-off-by: Ran Wang
> ---
> Change in v2:
> - For 'cn_development_coding' part, change back to '是关于编码过程的'
>
> .../translations/zh_CN/process/1.Intro.rst| 61 ++-
> 1 file changed, 32 insertions(+), 29 deletions(-)
On Tue, 8 Dec 2020 21:14:11 +0900
Masami Hiramatsu wrote:
> On Tue, 1 Dec 2020 16:06:56 -0500
> Steven Rostedt wrote:
>
> > From: Steven Rostedt (VMware)
> >
> > A bug was reported about the ftrace ring buffer going backwards:
> >
> > Link:
Hello,
Changes since v2:
* fixed typos
* introduce new colorimetry class
* kept the parameter validation (even though Hans suggested to drop it)
* rename to max/min_display_mastering_luminance
The previous patchset version can be found at [1].
regards,
Stan
[1]
Here we introduce a new Colorimetry control class and add
Content light level and Mastering display colour volume v4l2
compound controls, relevant payload structures and validation.
Signed-off-by: Stanimir Varbanov
---
.../media/videodev2.h.rst.exceptions | 2 +
Hello, Frederic,
Boqun just asked if RCU callbacks ran in BH-disabled context to avoid
concurrent execution of the same callback. Of course, this raises the
question of whether a self-posting callback can have two instances of
itself running concurrently while a CPU is in the process of
On Fri, Nov 20, 2020 at 11:14:11PM -0500, Waiman Long wrote:
> Waiman Long (5):
> locking/rwsem: Pass the current atomic count to
> rwsem_down_read_slowpath()
> locking/rwsem: Prevent potential lock starvation
> locking/rwsem: Enable reader optimistic lock stealing
> locking/rwsem:
Rob Herring 於 2020年12月8日 週二 上午12:42寫道：
>
> On Fri, Dec 04, 2020 at 12:06:33AM +0800, cy_huang wrote:
> > From: ChiYuan Huang
> >
> > Adds DT binding document for Richtek RT4831 backlight.
> >
> > Signed-off-by: ChiYuan Huang
> > ---
> > .../leds/backlight/richtek,rt4831-backlight.yaml | 86
Rob Herring 於 2020年12月8日 週二 上午12:41寫道：
>
> On Fri, Dec 04, 2020 at 12:06:35AM +0800, cy_huang wrote:
> > From: ChiYuan Huang
> >
> > Adds DT binding document for Richtek RT4831 MFD core.
> >
> > This patch depends on
> >
> > "backlight: rt4831: Adds DT binding document for Richtek RT4831
On 12/8/20 2:37 PM, Lukasz Luba wrote:
On 12/8/20 1:51 PM, Daniel Lezcano wrote:
Hi Lukasz,
On 08/12/2020 10:36, Lukasz Luba wrote:
Hi Daniel,
[ ... ]
static void thermal_zone_device_init(struct thermal_zone_device
*tz)
@@ -553,11 +555,9 @@ void
On 2020-12-03 16:47, Madalin Bucur wrote:
-Original Message-
From: Patrick Havelange
Sent: 03 December 2020 15:51
To: Madalin Bucur ; David S. Miller
; Jakub Kicinski ;
net...@vger.kernel.org; linux-kernel@vger.kernel.org
Cc: Patrick Havelange
Subject: [PATCH net 1/4] net:
On Mon, Dec 07, 2020 at 09:56:34AM -0600, Eric W. Biederman wrote:
> Do you want to pull these two into a topic branch in the tip tree
> based on v10-rc1?
I'll go do that. I'll let the robots chew on it before pushing it out
though, I'll reply once it's in tip.git.
On 12/8/20 3:43 PM, Hans de Goede wrote:
Hi,
On 12/8/20 3:37 PM, Maximilian Luz wrote:
+
+ obj = acpi_evaluate_dsm_typed(handle, _SSH_DSM_GUID,
+ SSAM_SSH_DSM_REVISION, func, NULL,
+ ACPI_TYPE_INTEGER);
+ if (!obj)
+ return -EIO;
+
+
Christophe Leroy writes:
> search_exception_tables() is an heavy operation, we have to avoid it.
> When KUAP is selected, we'll know the fault has been blocked by KUAP.
> Otherwise, it behaves just as if the address was already in the TLBs
> and no fault was generated.
>
> Signed-off-by:
On Mon, 2020-12-07 at 20:29 -0300, Marcelo Tosatti wrote:
> On Thu, Dec 03, 2020 at 07:11:16PM +0200, Maxim Levitsky wrote:
> > These two new ioctls allow to more precisly capture and
> > restore guest's TSC state.
> >
> > Both ioctls are meant to be used to accurately migrate guest TSC
> > even
On Tue, Dec 08, 2020 at 09:46:54AM +0530, Viresh Kumar wrote:
> Viresh Kumar (3):
> sched/core: Move schedutil_cpu_util() to core.c
> sched/core: Rename schedutil_cpu_util() and allow rest of the kernel
> to use it
> thermal: cpufreq_cooling: Reuse sched_cpu_util() for SMP platforms
How
No, this was sent by a b4 bug - notice the "no commit info" there, they
weren't applied.
Oh I see! I guess review would be still pending then.
I don't seem to have them in my backlog so either there was feedback
from someone else I was expecting to see addressed or some other issue.
I am
On 12/8/20 1:47 PM, zhangqing wrote:
>>> Add spi-ls7a binding documentation.
>>>
>>> Signed-off-by: Qing Zhang
>>> ---
>>> Documentation/devicetree/bindings/spi/spi-ls7a.txt | 31
>>> ++
>>> 1 file changed, 31 insertions(+)
>>> create mode 100644
On Tue, 8 Dec 2020 17:43:59 +0530, Manivannan Sadhasivam wrote:
> This series adds PCIe support for Qualcomm SM8250 SoC with relevant PHYs.
> There are 3 PCIe instances on this SoC each with different PHYs. The PCIe
> controller and PHYs are mostly comaptible with the ones found on SDM845
> SoC,
On Tue, 8 Dec 2020 at 14:54, Mel Gorman wrote:
>
> On Tue, Dec 08, 2020 at 02:43:10PM +0100, Vincent Guittot wrote:
> > On Tue, 8 Dec 2020 at 14:36, Mel Gorman wrote:
> > >
> > > On Tue, Dec 08, 2020 at 02:24:32PM +0100, Vincent Guittot wrote:
> > > > > > Nitpick:
> > > > > >
> > > > > > Since
Reduce a bit logging boilerplate by using the preferred pr_*()
macros instead of raw printk().
Signed-off-by: Enrico Weigelt, metux IT consult
---
drivers/usb/gadget/function/uvc.h | 2 +-
drivers/usb/gadget/udc/atmel_usba_udc.c | 2 +-
drivers/usb/gadget/udc/fsl_udc_core.c | 4 +--
Hi,
On 12/8/20 3:37 PM, Maximilian Luz wrote:
>>> +
>>> + obj = acpi_evaluate_dsm_typed(handle, _SSH_DSM_GUID,
>>> + SSAM_SSH_DSM_REVISION, func, NULL,
>>> + ACPI_TYPE_INTEGER);
>>> + if (!obj)
>>> + return -EIO;
>>> +
>>> + val =
Uwe, Thierry,
On Tue, Dec 8, 2020 at 4:10 AM Uwe Kleine-König
wrote:
>
> If this is already in the old code, this probably warrants a separate
> fix, and yes, I consider this a severe bug. (Consider one channel
> driving a motor and reconfiguring an LED modifies the motor's speed.)
>
I think
On 12/8/20 3:11 AM, Michael Ellerman wrote:
> "Enrico Weigelt, metux IT consult" writes:
>> All archs, except Alpha, print out the irq number in hex, but the message
>> looks like it was a decimal number, which is quite confusing. Fixing this
>> by adding "0x" prefix.
>
> Arguably decimal would
On 12/7/20 5:35 PM, Arnaldo Carvalho de Melo wrote:
> Em Tue, Nov 24, 2020 at 03:04:53PM +0530, Ravi Bangoria escreveu:
>>
>>
>> On 11/19/20 7:20 PM, Kajol Jain wrote:
>>> Commit ed21d6d7c48e6e ("perf tests: Add test for PE binary format support")
>>> adds a WINDOWS EXE file named
On Tue, Dec 8, 2020 at 4:19 PM Andy Shevchenko
wrote:
> On Tue, Dec 8, 2020 at 4:14 PM Enrico Weigelt, metux IT consult
> wrote:
> >
> > Many gpio drivers already use gpiolib's builtin irqchip handling
> > (CONFIG_GPIOLIB_IRQCHIP), but still has some boilerplate for retrieving
> > the actual
Srinivasan Raju writes:
> This introduces the pureLiFi LiFi driver for LiFi-X, LiFi-XC
> and LiFi-XL USB devices.
>
> This driver implementation has been based on the zd1211rw driver.
>
> Driver is based on 802.11 softMAC Architecture and uses
> native 802.11 for configuration and management.
>
On 12/8/20 1:51 PM, Daniel Lezcano wrote:
Hi Lukasz,
On 08/12/2020 10:36, Lukasz Luba wrote:
Hi Daniel,
[ ... ]
static void thermal_zone_device_init(struct thermal_zone_device *tz)
@@ -553,11 +555,9 @@ void thermal_zone_device_update(struct
thermal_zone_device *tz,
if
On 12/8/20 2:01 PM, Hans de Goede wrote:
Hi,
Thank you for your patch series.
Full review done, I have a couple of minor review remarks inline below.
Note these are really all suggestions and not must fix for this to
be merged items.
Thank you! I will try to address and fix them.
[...]
Peter?
-- Steve
On Tue, 8 Dec 2020 07:58:54 +
Tianxianting wrote:
> Thanks,
> We met an issue that a normal thread can't get cpu,
> And at this moment, we found 'sched: RT throttling activated' log.
>
> So I think this patch is useful for such issue.
>
> Could I get more comments?
Christophe Leroy writes:
> Le 08/12/2020 à 14:00, Aneesh Kumar K.V a écrit :
>> On 12/8/20 2:07 PM, Christophe Leroy wrote:
>>> search_exception_tables() is an heavy operation, we have to avoid it.
>>> When KUAP is selected, we'll know the fault has been blocked by KUAP.
>>> Otherwise, it
Dear,
I hereby officially invite you for inheritance claim belonging to late client.
I am inviting you because I have been mandated by his financial
institution here in my country where this fund was deposited to
present a surviving relative.
I will give you full details as soon you grant me
On Tue, Dec 08, 2020 at 06:31:12PM +0800, Boqun Feng wrote:
> These tests are added for two purposes:
>
> * Test the implementation of wait context checks and related
> annotations.
>
> * Semi-document the rules for wait context nesting when
> PROVE_RAW_LOCK_NESTING=y.
Currently ARCH_HAVE_NMI_SAFE_CMPXCHG is not set on Arm systems and this
makes it impossible to enable features such as ftrace histogram triggers
on Arm platforms.
Most Arm systems are NMI safe simply because there is no NMI but this isn't
universally true meaning we cannot set
Hi Jason,
On Mon, Dec 07, 2020 at 04:43:16PM -0400, Jason Gunthorpe wrote:
...
>
> The thing that was confusing is if it was appropriate to use a
> seqcount in case where write side preemption was not disabled - which
> is safe only if the read side doesn't spin.
>
No, that's not correct.
What
On Tue, Dec 08, 2020 at 05:20:35PM +0800, WANG Chao wrote:
> Sorry for the late reply.
>
> On 11/25/20 at 10:42P, Masahiro Yamada wrote:
> > On Tue, Nov 24, 2020 at 12:05 AM WANG Chao wrote:
> > >
> > > On 11/23/20 at 02:23P, Masahiro Yamada wrote:
> > > > On Tue, Nov 3, 2020 at 3:23 PM WANG
Xiaohui Zhang writes:
> From: Zhang Xiaohui
>
> mwifiex_config_scan() calls memcpy() without checking
> the destination size may trigger a buffer overflower,
> which a local user could use to cause denial of service
> or the execution of arbitrary code.
> Fix it by putting the length check
Xiaohui Zhang writes:
> From: Zhang Xiaohui
>
> mwifiex_uap_bss_param_prepare() calls memcpy() without checking
> the destination size may trigger a buffer overflower,
> which a local user could use to cause denial of service or the
> execution of arbitrary code.
> Fix it by putting the length
Le 08/12/2020 à 14:00, Aneesh Kumar K.V a écrit :
On 12/8/20 2:07 PM, Christophe Leroy wrote:
search_exception_tables() is an heavy operation, we have to avoid it.
When KUAP is selected, we'll know the fault has been blocked by KUAP.
Otherwise, it behaves just as if the address was already
On Mon, Dec 07, 2020 at 10:04:45AM -0800, Andy Lutomirski wrote:
>
> > On Dec 7, 2020, at 9:00 AM, Maxim Levitsky wrote:
> >
> > On Mon, 2020-12-07 at 08:53 -0800, Andy Lutomirski wrote:
> On Dec 7, 2020, at 8:38 AM, Thomas Gleixner wrote:
> >>>
> >>> On Mon, Dec 07 2020 at 14:16,
Move function for skipping host instruction in the host trap handler to
a header file containing analogical helpers for guests.
Signed-off-by: David Brazdil
---
arch/arm64/kvm/hyp/include/hyp/adjust_pc.h | 9 +
arch/arm64/kvm/hyp/nvhe/hyp-main.c | 12 ++--
2 files
Minor cleanup removing unused includes.
Signed-off-by: David Brazdil
---
arch/arm64/kvm/hyp/nvhe/psci-relay.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/arch/arm64/kvm/hyp/nvhe/psci-relay.c
b/arch/arm64/kvm/hyp/nvhe/psci-relay.c
index 0d6f4aa39621..1f7237e45148 100644
---
Computing the hyp VA layout is redundant when the kernel runs in EL2 and
hyp shares its VA mappings. Make calling kvm_compute_layout()
conditional on not just CONFIG_KVM but also !is_kernel_in_hyp_mode().
Signed-off-by: David Brazdil
---
arch/arm64/kernel/smp.c | 2 +-
1 file changed, 1
init_hyp_physvirt_offset() computes PA from a kernel VA. Conversion to
kernel linear-map is required first but the code used kvm_ksym_ref() for
this purpose. Under VHE that is a NOP and resulted in a runtime warning.
Replace kvm_ksym_ref with lm_alias.
Reported-by: Qian Cai
Signed-off-by: David
PSCI driver exposes a struct containing the PSCI v0.1 function IDs
configured in the DT. However, the struct does not convey the
information whether these were set from DT or contain the default value
zero. This could be a problem for PSCI proxy in KVM protected mode.
Extend config passed to KVM
Small cleanup moving declarations of hyp-exported variables to
kvm_host.h and using macros to avoid having to refer to them with
kvm_nvhe_sym() in host.
No functional change intended.
Signed-off-by: David Brazdil
---
arch/arm64/include/asm/kvm_host.h | 6 ++
arch/arm64/kvm/arm.c
On Thu, Dec 03, 2020 at 07:11:16PM +0200, Maxim Levitsky wrote:
> These two new ioctls allow to more precisly capture and
> restore guest's TSC state.
>
> Both ioctls are meant to be used to accurately migrate guest TSC
> even when there is a significant downtime during the migration.
>
>
Small batch of improvements for the 'Opt-in always-on nVHE hypervisor'
series, now merged in kvmarm/next.
Patch #1 fixes potential use of invalid v0.1 functions IDs reported
by Mark Rutland, patch #2 fixes a warning reported by Qian Cai.
Patch #3 avoids a code path not used in VHE, can be dropped
On Thu, Dec 03, 2020 at 07:11:15PM +0200, Maxim Levitsky wrote:
> Hi!
>
> This is the second version of the work to make TSC migration more accurate,
> as was defined by Paulo at:
> https://www.spinics.net/lists/kvm/msg225525.html
Maxim,
Can you please make a description of what is the
On Sun, Dec 06, 2020 at 05:19:16PM +0100, Thomas Gleixner wrote:
> On Thu, Dec 03 2020 at 19:11, Maxim Levitsky wrote:
> > + case KVM_SET_TSC_STATE: {
> > + struct kvm_tsc_state __user *user_tsc_state = argp;
> > + struct kvm_tsc_state tsc_state;
> > + u64 host_tsc,
Hi Daniel,
On 12/7/20 12:41 PM, Lukasz Luba wrote:
On 12/3/20 4:09 PM, Daniel Lezcano wrote:
On 03/12/2020 16:38, Lukasz Luba wrote:
On 12/3/20 1:09 PM, Daniel Lezcano wrote:
On 18/11/2020 13:03, Lukasz Luba wrote:
Devfreq cooling needs to now the correct status of the device in order
On 2020-12-07 11:57, Keqian Zhu wrote:
Although handling a mapping request with no permissions is a
trivial no-op, defer the early return until after the size/range
checks so that we are consistent with other mapping requests.
Reviewed-by: Robin Murphy
Signed-off-by: Keqian Zhu
---
On Tue, Dec 8, 2020 at 4:14 PM Enrico Weigelt, metux IT consult
wrote:
>
> Many gpio drivers already use gpiolib's builtin irqchip handling
> (CONFIG_GPIOLIB_IRQCHIP), but still has some boilerplate for retrieving
> the actual Linux IRQ number and calling into the generic handler.
> That
Many gpio drivers already use gpiolib's builtin irqchip handling
(CONFIG_GPIOLIB_IRQCHIP), but still has some boilerplate for retrieving
the actual Linux IRQ number and calling into the generic handler.
That boilerplate can be reduced by moving that into a helper function.
This is an RFC patch to
On Tue, Dec 08, 2020 at 09:49:57AM +0800, Aubrey Li wrote:
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index c4da7e17b906..b8af602dea79 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -3999,6 +3999,7 @@ void scheduler_tick(void)
> rq_lock(rq, );
>
>
On 12/8/20 12:13 AM, Krzysztof Kozlowski wrote:
> On Mon, Dec 07, 2020 at 04:19:16PM -0800, Guenter Roeck wrote:
>> On Mon, Dec 07, 2020 at 03:12:59PM -0600, Rob Herring wrote:
>>> On Tue, Nov 17, 2020 at 11:08:07PM +0100, Krzysztof Kozlowski wrote:
Convert the Analog Devices ADM1275 bindings
> > Hi Jean
> >
> > I never said i was too specific to your board. There are other boards
> > using different switches like this. This is where the commit message
> > is so important. Without understanding Why? it is hard to point you in
> > the right direction.
> >
> > So you setup is:
> >
> >
On Tue, 2020-12-08 at 21:56 +0800, Stanley Chu wrote:
> Since more and more statements showing up in
> ufshcd_vops_device_reset(),
> uninline it to allow compiler making possibly better optimization.
>
> Signed-off-by: Stanley Chu
reviewed-by: Bean Huo
On Tue, 2020-12-08 at 21:56 +0800, Stanley Chu wrote:
> index 08c8a591e6b0..36d367eb8139 100644
> --- a/drivers/scsi/ufs/ufshcd.h
> +++ b/drivers/scsi/ufs/ufshcd.h
> @@ -1221,8 +1221,13 @@ static inline void
> ufshcd_vops_device_reset(struct ufs_hba *hba)
> if (hba->vops &&
Ard Biesheuvel wrote:
> Apparently, it is permitted for gss_krb5_cts_crypt() to do a
> kmalloc(GFP_NOFS) in the context from where gss_krb5_aes_encrypt() is
> being invoked, and so I don't see why it wouldn't be possible to
> simply kmalloc() a scatterlist[] of the appropriate size, populate it
On Mon 2020-12-07 23:26:17, John Ogness wrote:
> Hello,
>
> Here is a v3 of the series to remove logbuf_lock. v2 is
> here[0]. Rather than completely removing logbuf_lock, this
> version only removes logbuf_lock usage protecting the
> ringbuffer. I have tried to keep the changes minimal so that
>
The firmware blob can contain optional ELF sections: .resource_table
section and .pru_irq_map one. The second one contains the PRUSS
interrupt mapping description, which needs to be setup before powering
on the PRU core. To avoid RAM wastage this ELF section is not mapped to
any ELF segment (by
From: Suman Anna
The remoteproc core creates certain standard debugfs entries,
that does not give a whole lot of useful information for the
PRUs. The PRU remoteproc driver is enhanced to add additional
debugfs entries for PRU. These will be auto-cleaned up when
the parent rproc debug directory
From: Suman Anna
The K3 J721E family of SoCs have a revised version of the AM65x ICSSG IP
and contains two instances of this newer ICSSG IP. Each ICSSG processor
subsystem contains 2 primary PRU cores, 2 auxiliary PRU cores called RTUs,
and 2 new auxiliary cores called Transmit PRUs (Tx_PRUs).
From: Suman Anna
The K3 AM65x family of SoCs have the next generation of the PRU-ICSS
processor subsystem, commonly referred to as ICSSG. Each ICSSG processor
subsystem on AM65x SR1.0 contains two primary PRU cores and two new
auxiliary PRU cores called RTUs. The AM65x SR2.0 SoCs have a revised
From: Suman Anna
The Programmable Real-Time Unit Subsystem (PRUSS) consists of
dual 32-bit RISC cores (Programmable Real-Time Units, or PRUs)
for program execution. This patch adds a remoteproc platform
driver for managing the individual PRU RISC cores life cycle.
The PRUs do not have a unified
801 - 900 of 1331 matches
Mail list logo
