On Mon, Jan 25, 2021 at 9:32 PM Greg Kroah-Hartman
wrote:
>
> On Sun, Jan 24, 2021 at 06:11:26PM +, Jonathan Cameron wrote:
> > On Fri, 22 Jan 2021 18:25:20 +0200
> > Alexandru Ardelean wrote:
> >
> > > When adding more than one IIO buffer per IIO device, we will need to
> > > create
> > > a
Excerpts from David Laight's message of January 25, 2021 10:24 pm:
> From: Christophe Leroy
>> Sent: 25 January 2021 09:15
>>
>> Le 24/01/2021 à 09:22, Nicholas Piggin a écrit :
>> > Support huge page vmalloc mappings. Config option HAVE_ARCH_HUGE_VMALLOC
>> > enables support on architectures that
Hi Rob,
On 1/25/21 10:40 PM, Rob Herring wrote:
On Thu, Jan 14, 2021 at 06:13:13PM +0100, Amelie Delaunay wrote:
usbphyc provides a unique clock called ck_usbo_48m.
STM32 USB OTG needs a 48Mhz clock (utmifs_clk48) for Full-Speed operation.
ck_usbo_48m is a possible parent clock for USB OTG 48Mh
Dear Guoqing,
On 26.01.21 01:44, Guoqing Jiang wrote:
Hi Donald,
On 1/25/21 22:32, Donald Buczek wrote:
On 25.01.21 09:54, Donald Buczek wrote:
Dear Guoqing,
a colleague of mine was able to produce the issue inside a vm and were able to
find a procedure to run the vm into the issue within
On 21-01-24 07:09:16, t...@redhat.com wrote:
> From: Tom Rix
>
> This change fixes the checkpatch warning described in this commit
> commit cbacb5ab0aa0 ("docs: printk-formats: Stop encouraging use of
> unnecessary %h[xudi] and %hh[xudi]")
>
> Standard integer promotion is already done and %hx
Currently, role init functions are used in dwc3 driver but
can't be called from kernel modules.
dwc3_host_init
dwc3_host_exit
dwc3_gadget_init
dwc3_gadget_exit
dwc3_event_buffers_setup
dwc3_event_buffers_cleanup
If other kernel modules want to use these functions, it needs
EXPORT_SYMBO
On 11/11/20 03:42, Xu, Like wrote:
Hi Peter,
On 2020/11/11 4:52, Stephane Eranian wrote:
On Tue, Nov 10, 2020 at 7:37 AM Peter Zijlstra
wrote:
On Tue, Nov 10, 2020 at 04:12:57PM +0100, Peter Zijlstra wrote:
On Mon, Nov 09, 2020 at 10:12:37AM +0800, Like Xu wrote:
The Precise Event Based Samp
On 26/01/2021 09.50, Greg Kroah-Hartman wrote:
> On Mon, Jan 25, 2021 at 08:59:54PM +0100, Rasmus Villemoes wrote:
>> On 25/01/2021 20.40, Rasmus Villemoes wrote:
>>> On 25/01/2021 19.39, Greg Kroah-Hartman wrote:
From: Rasmus Villemoes
commit 87fe04367d842c4d97a77303242d4dd4ac351e4
On 1/25/21 12:15 PM, Pavel Tatashin wrote:
> Currently, loop device has only one global lock:
> loop_ctl_mutex.
Above line can be :-
Currently, loop device has only one global lock: loop_ctl_mutex.
Also please provide a complete discretion what are the members it protects,
i.e. how big the size of
On 26.01.21 10:49, Michal Hocko wrote:
> On Tue 26-01-21 11:20:11, Mike Rapoport wrote:
>> On Tue, Jan 26, 2021 at 10:00:13AM +0100, Michal Hocko wrote:
>>> On Tue 26-01-21 10:33:11, Mike Rapoport wrote:
On Tue, Jan 26, 2021 at 08:16:14AM +0100, Michal Hocko wrote:
> On Mon 25-01-21 23:36:
Add a new common property 'reset-time-sec' to be used in conjunction
with the devices supporting the key pressed reset feature.
Signed-off-by: Cristian Ciocaltea
Reviewed-by: Rob Herring
---
Changes in v7:
- None
Changes in v6:
- None
Changes in v5:
- None
Changes in v4:
- Added Reviewed-
The Actions Semi ATC260x PMICs are able to manage an onkey button.
This driver exposes the ATC260x onkey as an input device. It can also
be configured to force a system reset on a long key-press with an
adjustable duration.
The currently supported chip variants are ATC2603C and ATC2609A.
Signed-o
On Tue, Jan 26, 2021 at 10:28:30AM +0100, Giovanni Gherdovich wrote:
> On Mon, 2021-01-25 at 11:04 +0100, Peter Zijlstra wrote:
> > On Fri, Jan 22, 2021 at 09:40:38PM +0100, Giovanni Gherdovich wrote:
> > > This workload is constant in time, so instead of using the PELT sum we can
> > > pretend tha
Hi Wolfram,
On Mon, Dec 28, 2020 at 1:03 PM Wolfram Sang
wrote:
> Not used anymore after refactoring:
>
> arch/arm/kernel/smp.c: In function ‘show_ipi_list’:
> arch/arm/kernel/smp.c:543:16: warning: variable ‘irq’ set but not used
> [-Wunused-but-set-variable]
> 543 | unsigned int irq;
>
> F
Hi Andrew,
The 01/22/2021 12:38, Andrew Jeffery wrote:
> Hi Troy,
>
> On Mon, 18 Jan 2021, at 17:20, Troy Lee wrote:
> > Add Aspeed AST2600 PWM/Fan tacho driver. AST2600 has 16 PWM channel and
> > 16 FAN tacho channel.
> >
> > Changes since v2:
> > - declare local function as static function
>
On Tue, Jan 26, 2021 at 09:31:40AM +, Mel Gorman wrote:
> So, should this patch be merged for 5.11 as a stopgap, fix up
> schedutil/cpufreq and then test both AMD and Intel chips reporting the
> correct max non-turbo and max-turbo frequencies? That would give time to
> give some testing in lin
On Mon, Jan 25, 2021 at 08:23:40PM +, Robin Murphy wrote:
> Now we probably will need some degreee of BBML feature awareness for the
> sake of SVA if and when we start using it for CPU pagetables, but I still
> cannot see any need to consider it in io-pgtable.
Agreed; I don't think this is som
Excerpts from Christophe Leroy's message of January 26, 2021 12:48 am:
> Only PPC64 has scv. No need to check the 0x7ff0 trap on PPC32.
>
> And ignore the scv parameter in syscall_exit_prepare (Save 14 cycles
> 346 => 332 cycles)
>
> Signed-off-by: Christophe Leroy
> ---
> arch/powerpc/kernel/e
On Tue, Jan 26, 2021 at 08:15:35AM +, Lee Jones wrote:
> On Mon, 25 Jan 2021, Cristian Ciocaltea wrote:
>
> > Hi Lee,
> >
> > On Mon, Jan 25, 2021 at 02:25:58PM +, Lee Jones wrote:
> > > On Wed, 20 Jan 2021, Cristian Ciocaltea wrote:
> > >
> > > > Add initial support for the Actions Semi
> On Jan 21, 2021, at 7:04 PM, Huaixin Chang
> wrote:
>
> Changelog
>
> v3:
> 1. Fix another issue reported by test robot.
> 2. Update docs as Randy Dunlap suggested.
>
> v2:
> 1. Fix an issue reported by test robot.
> 2. Rewriting docs. Appreciate any further suggestions or help.
>
> The
On Tue 26-01-21 10:53:08, David Hildenbrand wrote:
[...]
> I assume you've seen the benchmark results provided by Xing Zhengjun
>
> https://lore.kernel.org/linux-mm/213b4567-46ce-f116-9cdf-bbd0c884e...@linux.intel.com/
I was not. Thanks for the pointer. I will have a look.
--
Michal Hocko
SUSE
From: zuoqilin
Change 'exeeds' to 'exceeds'.
Signed-off-by: zuoqilin
---
drivers/power/supply/charger-manager.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/power/supply/charger-manager.c
b/drivers/power/supply/charger-manager.c
index 6fcebe4..731351d8 10064
On Mon, Jan 25, 2021 at 08:51:35AM -0600, Rob Herring wrote:
> On Mon, 25 Jan 2021 19:12:21 +0800, Xin Ji wrote:
> > Add 'bus-type' and 'data-lanes' define for port0, add HDCP support
> > flag and DP tx lane0 and lane1 swing register array define.
> >
> > Signed-off-by: Xin Ji
> > ---
> > .../bi
Excerpts from Christophe Leroy's message of January 26, 2021 12:48 am:
> syscall_64.c will be reused almost as is for PPC32.
>
> Rename it syscall.c
Could you rename it to interrupt.c instead? A system call is an
interrupt, and the file now also has code to return from other
interrupts as well,
On Mon, 25 Jan 2021 14:38:56 +0200 Oleksandr Mazur wrote:
> + if (trap_item->action == DEVLINK_TRAP_ACTION_DROP &&
> + devlink->ops->trap_drop_counter_get) {
> + err = devlink->ops->trap_drop_counter_get(devlink,
> + trap
On Tue, Jan 26, 2021 at 12:17:21PM +0200, Nikolay Borisov wrote:
> This is a leftover from 7f26482a872c ("locking/percpu-rwsem: Remove the
> embedded rwsem")
>
> Signed-off-by: Nikolay Borisov
> ---
> V2:
> * Add reference to commit which made the file useless.
>
> kernel/locking/rwsem.h | 0
On Mon 2021-01-25 09:17:48, Lukas Bulwahn wrote:
> The command 'find ./kernel/printk/ | xargs ./scripts/kernel-doc -none'
> reported a mismatch with the kernel-doc of prb_rec_init_wr().
>
> Rectify the kernel-doc, such that no issues remain for ./kernel/printk/.
>
> Signed-off-by: Lukas Bulwahn
On 2021/01/26 18:37, Changheun Lee wrote:
> bio size can grow up to 4GB when muli-page bvec is enabled.
> but sometimes it would lead to inefficient behaviors.
> in case of large chunk direct I/O, - 32MB chunk read in user space -
> all pages for 32MB would be merged to a bio structure if the pages
From: Nicholas Piggin
> Sent: 26 January 2021 10:21
>
> Excerpts from Christophe Leroy's message of January 26, 2021 12:48 am:
> > syscall_64.c will be reused almost as is for PPC32.
> >
> > Rename it syscall.c
>
> Could you rename it to interrupt.c instead? A system call is an
> interrupt, and t
On 2021-01-25 21:52, Isaac J. Manjarres wrote:
When extracting the mask for a SMR that was programmed by the
bootloader, the SMR's valid bit is also extracted and is treated
as part of the mask, which is not correct. Consider the scenario
where an SMMU master whose context is determined by a boot
The new fields inside devfreq struct allow to check the frequency limits
set by the user via sysfs. These limits are important for thermal governor
Intelligent Power Allocation (IPA) which needs to know the maximum allowed
power consumption of the device.
Signed-off-by: Lukasz Luba
---
drivers/d
From: dingsenjie
allocted -> allocated
Signed-off-by: dingsenjie
---
drivers/scsi/megaraid/megaraid_mbox.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/megaraid/megaraid_mbox.c
b/drivers/scsi/megaraid/megaraid_mbox.c
index 4a27ac8..d57e938 100644
--- a/driv
User can limit the maximum frequency of the device via sysfs interface.
It limits also corresponding maximum allowed power consumption. The IPA
governor needs to know maximum power of the device to split the budget.
If the user limit is not provided, some power is wasted while it could
be added to
Am 2021-01-26 11:02, schrieb Lorenzo Pieralisi:
On Wed, Jan 20, 2021 at 11:52:46AM +0100, Michael Walle wrote:
fw_devlink will defer the probe until all suppliers are ready. We
can't
use builtin_platform_driver_probe() because it doesn't retry after
probe
deferral. Convert it to builtin_platfo
Hi all,
This patch set tries to add the missing feature in the Intelligent Power
Allocation (IPA) governor which is: frequency limit set by user space.
User can set max allowed frequency for a given device which has impact on
max allowed power. In current design there is no mechanism to figure thi
Use new API interface to get the maximum power of the cooling device. This
is needed to properly allocate and split the total power budget. The
allowed limit is taken from supported cooling device and then checked with
limits set in DT. The final state value is used for asking for the related
power
On Fri, 22 Jan 2021, Jiri Kosina wrote:
> > > This series adds a document, mainly written by Mark Rutland, which
> > > makes explicit the requirements for implementing reliable stacktrace
> > > in order to aid architectures adding this feature. It also updates
> > > the other livepatching docu
Suppose that I/O dispatch is plugged, to wait for new I/O for the
in-service bfq-queue, say bfqq. Suppose then that there is a further
bfq_queue woken by bfqq, and that this woken queue has pending I/O. A
woken queue does not steal bandwidth from bfqq, because it remains
soon without I/O if bfqq i
Many throughput-sensitive workloads are made of several parallel I/O
flows, with all flows generated by the same application, or more
generically by the same task (e.g., system boot). The most
counterproductive action with these workloads is plugging I/O dispatch
when one of the bfq_queues associat
From: Biwen Li
Add flag IRQCHIP_SKIP_SET_WAKE to remove call trace as follow,
[ 45.605239] Unbalanced IRQ 120 wake disable
[ 45.609445] WARNING: CPU: 0 PID: 1124 at kernel/irq/manage.c:800
irq_set_irq_wake+0x154/0x1a0
[ 45.617965] Modules linked in: fsl_jr_uio caam_jr caamkeyblob_desc
cry
Hi,
When fuzzing arm64 with Syzkaller, I'm seeing some splats where
this_cpu_ptr() is used in the bowels of idr_alloc(), by way of
radix_tree_node_alloc(), in a preemptible context:
| BUG: using smp_processor_id() in preemptible [] code:
syz-executor.1/32582
| caller is debug_smp_process
On Wed, 20 Jan 2021 11:52:46 +0100, Michael Walle wrote:
> fw_devlink will defer the probe until all suppliers are ready. We can't
> use builtin_platform_driver_probe() because it doesn't retry after probe
> deferral. Convert it to builtin_platform_driver().
Applied to pci/dwc, thanks!
[1/1] PCI:
When the io_latency heuristic is off, bfq_queues must not start to be
weight-raised. Unfortunately, by mistake, this may happen when the
state of a previously weight-raised bfq_queue is resumed after a queue
split. This commit fixes this error.
Tested-by: Jan Kara
Signed-off-by: Paolo Valente
--
Hi Michael,
On Tue, Jan 26, 2021 at 11:46 AM Michael Walle wrote:
> Am 2021-01-26 11:02, schrieb Lorenzo Pieralisi:
> > On Wed, Jan 20, 2021 at 11:52:46AM +0100, Michael Walle wrote:
> >> fw_devlink will defer the probe until all suppliers are ready. We
> >> can't
> >> use builtin_platform_driver
A test with the command below aimed at powerpc generates
notifications in the Rockchip ARM tree.
Fix pinctrl "sleep" nodename by renaming it to "suspend"
for rk3036-kylin and rk3288
make ARCH=arm dtbs_check
DT_SCHEMA_FILES=Documentation/devicetree/bindings/powerpc/sleep.yaml
Signed-off-by: Johan
On 25/01/2021 11:50, Song Bao Hua (Barry Song) wrote:
>
>> -Original Message-
>> From: Dietmar Eggemann [mailto:dietmar.eggem...@arm.com]
>> Sent: Wednesday, January 13, 2021 12:00 AM
>> To: Morten Rasmussen ; Tim Chen
>>
>> Cc: Song Bao Hua (Barry Song) ;
>> valentin.schnei...@arm.com; c
The axi-clkgen driver now supports ZynqMP (UltraScale) as well, however the
driver needs to use different PFD & VCO limits.
For ZynqMP, these needs to be selected by using the
'adi,zynqmp-axi-clkgen-2.00.a' string.
Signed-off-by: Alexandru Ardelean
---
Documentation/devicetree/bindings/clock/ad
For ZynqMP (Ultrascale) the PFD and VCO limits are different. In order to
support these, this change adds a compatible string (i.e.
'adi,zynqmp-axi-clkgen-2.00.a') which will take into account for these
limits and apply them.
Signed-off-by: Dragos Bogdan
Signed-off-by: Mathias Tausen
Signed-off
Previous set:
https://lore.kernel.org/linux-clk/20201221144224.50814-1-alexandru.ardel...@analog.com/
Changelog v1 -> v2:
* split patch 'clk: axi-clkgen: add support for ZynqMP (UltraScale)'
into:
- clk: axi-clkgen: remove ARCH dependency in Kconfig
- clk: clk-axiclkgen: add ZynqMP PFD a
On Tue, Jan 26, 2021 at 05:17:08PM +0800, Lecopzer Chen wrote:
> Hi all,
>
> I don't see any fix for this issue now(maybe I missed it..?),
> could we fix this if there is better solution?
> This issue exists almost two years.
I don't think anyone provided an acceptable patch.
The first patch mov
On 2021-01-26 10:59:32 [+], Russell King - ARM Linux admin wrote:
> On Tue, Jan 26, 2021 at 05:17:08PM +0800, Lecopzer Chen wrote:
> > Hi all,
> >
> > I don't see any fix for this issue now(maybe I missed it..?),
> > could we fix this if there is better solution?
> > This issue exists almost t
* André Hentschel [201227 19:18]:
> This adds audio playback to the first generation Amazon Echo
>
> Signed-off-by: André Hentschel
> ---
>
> It took me by far too long to get this working as the codec sets one
> important bit based on the
> combination of provided supplies. That was just too
Hi Donald,
On 1/26/21 10:50, Donald Buczek wrote:
[...]
diff --git a/drivers/md/md.c b/drivers/md/md.c
index 2d21c298ffa7..f40429843906 100644
--- a/drivers/md/md.c
+++ b/drivers/md/md.c
@@ -4687,11 +4687,13 @@ action_store(struct mddev *mddev, const char
*page, size_t len)
cle
Hi Oliver,
On Mon, Jan 25, 2021 at 7:17 PM Oliver Graute wrote:
> I would prefer mine, because I got a wrong colored penguin on bootup
> with yours :-)
I have originally passed .bpc = 8, but looking at the panel datasheet,
this should be:
.bpc = 6 instead.
In your patch, you pass the timing pa
Some clocks are already enabled in HW even before the kernel
starts to boot. So, in order to make sure that these clocks do not
get disabled when clk_disable_unused call is done or when
reparenting clocks, we enable them in core on clock registration.
Such a clock will have to be registered with CL
On Tue, Jan 26, 2021 at 04:43:51PM +0530, Naresh Kamboju wrote:
> On Tue, 26 Jan 2021 at 15:33, Greg Kroah-Hartman
> wrote:
> >
> > This is the start of the stable review cycle for the 5.4.93 release.
> > There are 88 patches in this series, all will be posted as a response
> > to this one. If an
On 23.01.21 08:05, Miaohe Lin wrote:
Commit 108bcc96ef70 ("mm: add & use zone_end_pfn() and zone_spans_pfn()")
introduced the helper zone_end_pfn() to calculate the zone end pfn. But
pagetypeinfo_showmixedcount_print forgot to use it. And the initialization
of local variable pfn is duplicated, re
* Adam Ford [210109 19:01]:
> Previously, the 1GHz variants were marked as a turbo,
> because that variant has reduced thermal operating range.
>
> Now that the thermal throttling is in place, it should be
> safe to remove the turbo-mode from the 1GHz variants, because
> the CPU will automaticall
On Tue, 26 Jan 2021 at 16:46, Greg Kroah-Hartman
wrote:
>
> On Tue, Jan 26, 2021 at 04:43:51PM +0530, Naresh Kamboju wrote:
> > On Tue, 26 Jan 2021 at 15:33, Greg Kroah-Hartman
> > wrote:
> > >
> > > This is the start of the stable review cycle for the 5.4.93 release.
> > > There are 88 patches i
Will Deacon wrote:
> > @@ -219,9 +235,14 @@ static inline void refcount_add(int i, r
> > *
> > * Return: true if the increment was successful, false otherwise
> > */
> > +static inline __must_check bool __refcount_inc_not_zero(refcount_t *r, int
> > *oldp)
> > +{
> > + return __refcount_
On 2021/1/26 17:51, Paolo Bonzini wrote:
On 11/11/20 03:42, Xu, Like wrote:
Hi Peter,
On 2020/11/11 4:52, Stephane Eranian wrote:
On Tue, Nov 10, 2020 at 7:37 AM Peter Zijlstra
wrote:
On Tue, Nov 10, 2020 at 04:12:57PM +0100, Peter Zijlstra wrote:
On Mon, Nov 09, 2020 at 10:12:37AM +0800, L
Pointers to receive-buffer packets sent by Hyper-V are used within the
guest VM. Hyper-V can send packets with erroneous values or modify
packet fields after they are processed by the guest. To defend against
these scenarios, copy (sections of) the incoming packet after validating
their length an
On 26/01/21, Arnd Bergmann wrote:
> On Tue, Jan 26, 2021 at 9:08 AM Jorge Ramirez-Ortiz, Foundries
> wrote:
> >
> > On 25/01/21, Arnd Bergmann wrote:
> > > From: Arnd Bergmann
> > >
> > > Storing a bogus i2c_client structure on the stack adds overhead and
> > > causes a compile-time warning:
> >
On Mon, Dec 14, 2020 at 03:13:12PM +0100, Stefan Saecherl wrote:
> One thing to consider when doing this is that code can go away during boot
> (e.g. .init.text). Previously kgdb_arch_remove_breakpoint handled this case
> gracefully by just having copy_to_kernel_nofault fail but if one then calls
Hi!
> This is the start of the stable review cycle for the 5.10.11 release.
> There are 203 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Thu, 28 Jan 2021 09:42:40 +
On 26/01/21 09:18, Wei Huang wrote:
@@ -288,6 +290,9 @@ int svm_set_efer(struct kvm_vcpu *vcpu, u64 efer)
if (!(efer & EFER_SVME)) {
svm_leave_nested(svm);
svm_set_gif(svm, true);
+ /* #GP intercept is still ne
Hi Wolfram,
On Sat, 2021-01-09 at 16:29 +0800, qii.w...@mediatek.com wrote:
> From: Qii Wang
>
> Some i2c device driver indirectly uses I2C driver when it is now
> being suspended. The i2c devices driver is suspended during the
> NOIRQ phase and this cannot be changed due to other dependencies.
On Thu 21-01-21 14:27:19, Mike Rapoport wrote:
> From: Mike Rapoport
>
> Removing a PAGE_SIZE page from the direct map every time such page is
> allocated for a secret memory mapping will cause severe fragmentation of
> the direct map. This fragmentation can be reduced by using PMD-size pages
> a
On Tue, Jan 26, 2021 at 11:04:47AM +0100, Geert Uytterhoeven wrote:
> Hi Wolfram,
>
> On Mon, Dec 28, 2020 at 1:03 PM Wolfram Sang
> wrote:
> > Not used anymore after refactoring:
> >
> > arch/arm/kernel/smp.c: In function ‘show_ipi_list’:
> > arch/arm/kernel/smp.c:543:16: warning: variable ‘irq’
Hi all,
Commits
daa94e1d8977 ("NFS: Convert readpage to readahead and use netfs_readahead for
fscache")
08a636bcf023 ("NFS: Convert to the netfs API and nfs_readpage to use
netfs_readpage")
56ee45bd6a23 ("NFS: Allow internal use of read structs and functions")
31d24fb6dff4 ("NFS: Add nf
On 2021-01-25 21:51, Jordan Crouse wrote:
On Fri, Jan 22, 2021 at 12:53:17PM +, Robin Murphy wrote:
On 2021-01-22 12:41, Will Deacon wrote:
On Tue, Nov 24, 2020 at 12:15:58PM -0700, Jordan Crouse wrote:
Call report_iommu_fault() to allow upper-level drivers to register their
own fault hand
On Mon, 2021-01-25 at 13:54 -0600, Rob Herring wrote:
> On Wed, Jan 13, 2021 at 07:39:57PM +0800, Jianjun Wang wrote:
> > MediaTek's PCIe host controller has three generation HWs, the new
> > generation HW is an individual bridge, it supports Gen3 speed and
> > compatible with Gen2, Gen1 speed.
> >
On 26/01/21 09:18, Wei Huang wrote:
While running SVM related instructions (VMRUN/VMSAVE/VMLOAD), some AMD
CPUs check EAX against reserved memory regions (e.g. SMM memory on host)
before checking VMCB's instruction intercept. If EAX falls into such
memory areas, #GP is triggered before #VMEXIT. T
* Wang Qing [200917 10:49]:
> Change the comment typo: "ununsed" -> "unused".
Sorry looks like this is still pending, applying into omap-for-v5.12/soc.
Thanks,
Tony
On 26/01/21 09:18, Wei Huang wrote:
Under the case of nested on nested (L0->L1->L2->L3), #GP triggered by
SVM instructions can be hided from L1. Instead the hypervisor can inject
the proper #VMEXIT to inform L1 of what is happening. Thus L1 can avoid
invoking the #GP workaround. For this reason
On Tue, Jan 26, 2021 at 01:21:36PM +0200, Abel Vesa wrote:
> Some clocks are already enabled in HW even before the kernel
> starts to boot. So, in order to make sure that these clocks do not
> get disabled when clk_disable_unused call is done or when
> reparenting clocks, we enable them in core on
On Tue, 2021-01-26 at 03:18 -0500, Wei Huang wrote:
> From: Bandan Das
>
> While running SVM related instructions (VMRUN/VMSAVE/VMLOAD), some AMD
> CPUs check EAX against reserved memory regions (e.g. SMM memory on host)
> before checking VMCB's instruction intercept. If EAX falls into such
> mem
On 2021/1/26 17:47, Nicholas Piggin wrote:
> Excerpts from Ding Tianhong's message of January 26, 2021 4:59 pm:
>> On 2021/1/26 12:45, Nicholas Piggin wrote:
>>> Support huge page vmalloc mappings. Config option HAVE_ARCH_HUGE_VMALLOC
>>> enables support on architectures that define HAVE_ARCH_HUGE_
On Tue, 2021-01-26 at 03:18 -0500, Wei Huang wrote:
> New AMD CPUs have a change that checks #VMEXIT intercept on special SVM
> instructions before checking their EAX against reserved memory region.
> This change is indicated by CPUID_0x800A_EDX[28]. If it is 1, #VMEXIT
> is triggered before #G
On Tue, Jan 26, 2021 at 10:51:39AM +0100, Paolo Bonzini wrote:
> What is the state of this work? I was expecting a new version that doesn't
> use counter_freezing. However, I see that counter_freezing is still in
> there, so this patch from Peter has never been applied.
Bah, I forgot about it. L
On 1/25/21 5:56 PM, Catalin Marinas wrote:
> On Mon, Jan 25, 2021 at 04:09:57PM +, Vincenzo Frascino wrote:
>> On 1/25/21 2:59 PM, Catalin Marinas wrote:
>>> On Mon, Jan 25, 2021 at 02:36:34PM +, Vincenzo Frascino wrote:
On 1/25/21 1:02 PM, Mark Rutland wrote:
> On Fri, Jan 22,
This patchset is to fix the failure of deferred attach for iommu attach
device, it includes the following two patches:
[1] [PATCH 1/2] dma-iommu: use static-key to minimize the impact in the
fast-path
This is a prepared patch for the second one, move out the is_kdump_kernel()
check from i
Hi Zenghui,
On Fri, Dec 25, 2020 at 8:05 AM Zenghui Yu wrote:
> On 2020/12/15 18:30, Geert Uytterhoeven wrote:
> > arch/arm64/kernel/smp.c: In function ‘arch_show_interrupts’:
> > arch/arm64/kernel/smp.c:808:16: warning: unused variable ‘irq’
> > [-Wunused-variable]
> >808 |
Let's move out the is_kdump_kernel() check from iommu_dma_deferred_attach()
to iommu_dma_init(), and use the static-key in the fast-path to minimize
the impact in the normal case.
Signed-off-by: Lianbo Jiang
Co-developed-by: Robin Murphy
Signed-off-by: Robin Murphy
---
drivers/iommu/dma-iommu.
Currently, because domain attach allows to be deferred from iommu
driver to device driver, and when iommu initializes, the devices
on the bus will be scanned and the default groups will be allocated.
Due to the above changes, some devices could be added to the same
group as below:
[3.859417]
When subpool max_hpages accounting is not enabled, used_hpages is always 0
and might lead to release subpool prematurely because it indicates no pages
are used now while there might be.
In order to fix this issue, we should check used_hpages == 0 iff max_hpages
accounting is enabled. As max_hpages
On Tue, Jan 26, 2021 at 06:26:02AM +, Damien Le Moal wrote:
> On 2021/01/26 15:07, Ming Lei wrote:
> > On Tue, Jan 26, 2021 at 04:06:06AM +, Damien Le Moal wrote:
> >> On 2021/01/26 12:58, Ming Lei wrote:
> >>> On Tue, Jan 26, 2021 at 10:32:34AM +0900, Changheun Lee wrote:
> bio size c
On Tue, 2021-01-26 at 19:54 +1100, Stephen Rothwell wrote:
> Hi all,
>
> Commit
>
> 98d2c3e17310 ("Bluetooth: L2CAP: Try harder to accept device not
> knowing options")
>
> is missing a Signed-off-by from its author.
Marcel, is it possible to amend this to add my Signed-off-by?
Signed-off-by
Restrict the NVSP protocol version(s) that will be negotiated with the
host to be NVSP_PROTOCOL_VERSION_61 or greater if the guest is running
isolated. Moreover, do not advertise the SR-IOV capability and ignore
NVSP_MSG_4_TYPE_SEND_VF_ASSOCIATION messages in isolated guests, which
are not suppose
Only the VSCs or ICs that have been hardened and that are critical for
the successful adoption of Confidential VMs should be allowed if the
guest is running isolated. This change reduces the footprint of the
code that will be exercised by Confidential VMs and hence the exposure
to bugs and vulnera
On 08/01/21 02:36, Like Xu wrote:
@@ -401,6 +398,9 @@ static void intel_pmu_init(struct kvm_vcpu *vcpu)
pmu->fixed_counters[i].idx = i + INTEL_PMC_IDX_FIXED;
pmu->fixed_counters[i].current_config = 0;
}
+
+ vcpu->arch.perf_capabilities = guest_cpuid_
Restrict the protocol version(s) that will be negotiated with the host
to be 5.2 or greater if the guest is running isolated. This reduces the
footprint of the code that will be exercised by Confidential VMs and
hence the exposure to bugs and vulnerabilities.
Signed-off-by: Andrea Parri (Microsof
Excerpts from Ding Tianhong's message of January 26, 2021 4:59 pm:
> On 2021/1/26 12:45, Nicholas Piggin wrote:
>> Support huge page vmalloc mappings. Config option HAVE_ARCH_HUGE_VMALLOC
>> enables support on architectures that define HAVE_ARCH_HUGE_VMAP and
>> supports PMD sized vmap mappings.
>>
Changes since v1 [1]:
- improve/add logging (Haiyang Zhang)
- move NVSC version check after version negotiation (Haiyang Zhang)
[1] https://lkml.kernel.org/r/20210119175841.22248-1-parri.and...@gmail.com
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Cc: "H. Peter Anvin"
Cc: Arnd
If bit 22 of Group B Features is set, the guest has access to the
Isolation Configuration CPUID leaf. On x86, the first four bits
of EAX in this leaf provide the isolation type of the partition;
we entail three isolation types: 'SNP' (hardware-based isolation),
'VBS' (software-based isolation), an
On 26.01.21 12:46, Michal Hocko wrote:
On Thu 21-01-21 14:27:19, Mike Rapoport wrote:
From: Mike Rapoport
Removing a PAGE_SIZE page from the direct map every time such page is
allocated for a secret memory mapping will cause severe fragmentation of
the direct map. This fragmentation can be red
On 26/01/21 12:35, Xu, Like wrote:
Ah, now we have the v3 version on guest PEBS feature.
It does not rely on counter_freezing, but disables the co-existence of
guest PEBS and host PEBS.
I am not clear about your attitude towards this co-existence.
There are also more interesting topics for
Let's make "MEMHP_MERGE_RESOURCE" consistent with "MHP_NONE", "mhp_t" and
"mhp_flags". As discussed recently [1], "mhp" is our internal
acronym for memory hotplug now.
[1]
https://lore.kernel.org/linux-mm/c37de2d0-28a1-4f7d-f944-cfd7d81c3...@redhat.com/
Cc: Andrew Morton
Cc: "K. Y. Srinivasan"
On Tue, 2021-01-26 at 03:18 -0500, Wei Huang wrote:
> Under the case of nested on nested (L0->L1->L2->L3), #GP triggered by
> SVM instructions can be hided from L1. Instead the hypervisor can
> inject the proper #VMEXIT to inform L1 of what is happening. Thus L1
> can avoid invoking the #GP workaro
On Mon, 2021-01-25 at 14:22 -0600, Rob Herring wrote:
> On Wed, Jan 13, 2021 at 07:39:55PM +0800, Jianjun Wang wrote:
> > Add YAML schemas documentation for Gen3 PCIe controller on
> > MediaTek SoCs.
> >
> > Signed-off-by: Jianjun Wang
> > Acked-by: Ryder Lee
> > ---
> > .../bindings/pci/mediat
501 - 600 of 2082 matches
Mail list logo
