(Note: this is version 1; there's a later version posted, which does
not have a v2 tag...)
https://lore.kernel.org/linux-wireless/20201208150951.35866-1-ruc_zhangxiao...@163.com/
On Sat, Jan 9, 2021 at 7:11 AM Peter Seiderer wrote:
> On Tue, 8 Dec 2020 20:45:23 +0800, Xiaohui Zhang
> wrote:
On Mon 11 Jan 11:43 CST 2021, Vinod Koul wrote:
> On 11-01-21, 09:34, Bjorn Andersson wrote:
> > On Mon 11 Jan 09:16 CST 2021, Vinod Koul wrote:
> >
> > > I2C geni driver needs to access struct geni_wrapper, so move it to
> > > header.
> > >
> >
> > Please tell me more!
> >
> > Glanced
On Sun, Jan 10, 2021 at 07:41:02PM +0100, Pavel Machek wrote:
> Hi!
>
> On Fri 2020-10-09 10:37:32, Theodore Y. Ts'o wrote:
> > On Thu, Oct 08, 2020 at 03:22:59PM -0700, Josh Triplett wrote:
> > >
> > > I wasn't trying to make a *new* general principle or policy. I was under
> > > the impression
On Mon, Jan 11, 2021 at 07:33:15PM +0100, Greg KH wrote:
> On Mon, Jan 11, 2021 at 06:20:29PM +, Matthew Wilcox wrote:
> > > efficient in what way? Space or faster lookup?
> >
> > Both, but primarily space.
> >
> > The radix tree underlying the xarray allows N consecutive entries with
> >
Hi,
since 5.11-rc1 I get kernel crashes with infinite recursion in
device_reorder_to_tail() in some situations... It's a bit complicated to
explain so I want to apologize in advance for the long mail. :)
Kernel panic - not syncing: kernel stack overflow
CPU: 1 PID: 33 Comm: kworker/1:1 Not
Il 11/01/21 14:16, Mark Brown ha scritto:
On Sat, Jan 09, 2021 at 02:29:15PM +0100, AngeloGioacchino Del Regno wrote:
+ .linear_ranges = (struct linear_range[]) {
+ REGULATOR_LINEAR_RANGE(460, 0, 15, 10),
+ },
+ .n_linear_ranges= 1,
If
On Wed, Jan 6, 2021 at 3:35 AM Kirill Tkhai wrote:
>
> On 06.01.2021 01:58, Yang Shi wrote:
> > Now shrinker's nr_deferred is per memcg for memcg aware shrinkers, add to
> > parent's
> > corresponding nr_deferred when memcg offline.
> >
> > Signed-off-by: Yang Shi
> > ---
> >
Hi Marc,
On Mon, Jan 11, 2021 at 01:27:59PM +, Marc Zyngier wrote:
> Add a facility to globally override a feature, no matter what
> the HW says. Yes, this is dangerous.
Yeah, it's dangerous. We can make it less so if we only allow safe
values (e.g. lower if FTR_UNSIGNED).
> diff --git
On Wed, Jan 6, 2021 at 3:16 AM Kirill Tkhai wrote:
>
> On 06.01.2021 01:58, Yang Shi wrote:
> > Now nr_deferred is available on per memcg level for memcg aware shrinkers,
> > so don't need
> > allocate shrinker->nr_deferred for such shrinkers anymore.
> >
> > The prealloc_memcg_shrinker() would
On Fri, 2021-01-08 at 19:05 +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> On x86 scale invariace tends to be disabled during resume from
> suspend-to-RAM, because the MPERF or APERF MSR values are not as
> expected then due to updates taking place after the platform
> firmware
On Mon, Jan 11, 2021 at 09:06:22AM -0800, Suren Baghdasaryan wrote:
> process_madvise currently requires ptrace attach capability.
> PTRACE_MODE_ATTACH gives one process complete control over another
> process. It effectively removes the security boundary between the
> two processes (in one
On Mon, Jan 11, 2021 at 06:20:29PM +, Matthew Wilcox wrote:
> On Mon, Jan 11, 2021 at 07:11:25PM +0100, Greg KH wrote:
> > On Mon, Jan 11, 2021 at 05:35:00PM +, Matthew Wilcox wrote:
> > > On Mon, Jan 11, 2021 at 06:05:13PM +0100, Christoph Hellwig wrote:
> > > > None of the complicated
On Tue, 5 Jan 2021 15:19:45 +, Sudeep Holla wrote:
> Cristian is actively developing new features and more involved than me.
> So add Cristian as a designated reviewer. Also add the newly added scmi
> regulator driver to the list.
Applied to sudeep.holla/linux (for-next/scmi), thanks!
[1/1]
On Tue, 22 Dec 2020 09:56:01 -0500, Jim Quinlan wrote:
> v4 -- s/message-serviced/a2p/ in the bindings commit message.
>-- Changed author/s-o-b/committer email address as my company is now
> appending boilerplate text to all outgoing emails.
>
> v3 -- Changed interrupt name from
Resent due to gmail adding HTML, sorry for the noise.
Am Montag, den 11.01.2021, 18:49 +0100 schrieb
Ahmad Fatoum:
>
> On 11.01.21 16:17, Max Krummenacher wrote:
> > When the kernel is configured to use the Thumb-2 instruction set
> > "suspend-to-memory" fails to resume. Observed on a Colibri
Instead of unconditional queueing of ready-to-consume skbuff_heads
to flush_skb_cache, feed skb_cache with them instead if it's not
full already.
This greatly reduces the frequency of kmem_cache_alloc_bulk() calls.
Signed-off-by: Alexander Lobakin
---
net/core/skbuff.c | 5 +
1 file
The Awinic AW9523(B) is a multi-function I2C gpio expander in a
TQFN-24L package, featuring PWM (max 37mA per pin, or total max
power 3.2Watts) for LED driving capability.
It has two ports with 8 pins per port (for a total of 16 pins),
configurable as either PWM with 1/256 stepping or GPIO
Add bindings for the Awinic AW9523/AW9523B I2C GPIO Expander driver.
Signed-off-by: AngeloGioacchino Del Regno
---
.../pinctrl/awinic,aw9523-pinctrl.yaml| 112 ++
1 file changed, 112 insertions(+)
create mode 100644
On 1/10/21 1:11 AM, Hyunwook (Wooky) Baek wrote:
Don't assume dest/source buffers are userspace addresses when manually
copying data for string I/O or MOVS MMIO, as {get,put}_user() will fail
if handed a kernel address and ultimately lead to a kernel panic.
Signed-off-by: Hyunwook (Wooky) Baek
Use the same napi_alloc_cache struct and the same approach as used
for bulk-freeing skbuff_heads to allocate them for new skbs.
The new skb_cache will store up to NAPI_SKB_CACHE_SIZE (currently
64, which equals to NAPI_POLL_WEIGHT to be capable to serve one
polling cycle) and will be refilled by
Instead of unconditional allocating a new skbuff_head and
unconditional flushing of flush_skb_cache, reuse the ones queued
up for flushing if there are any.
skbuff_heads stored in flush_skb_cache are already unreferenced
from any pages or extensions and almost ready for use. We perform
zeroing in
In preparation for skbuff_heads caching and reusing, open-code
__build_skb() inside __napi_alloc_skb() with factoring out
the skbbuff_head allocation itself.
Note that the return value of __build_skb_around() is not checked
since it never returns anything except the given skb.
Signed-off-by:
On Mon, Jan 11, 2021 at 10:57:35AM +0100, Sedat Dilek wrote:
> On Mon, Jan 11, 2021 at 10:17 AM Bill Wendling wrote:
> >
> > On Mon, Jan 11, 2021 at 12:39 AM Sedat Dilek wrote:
> > >
> > > On Mon, Jan 11, 2021 at 9:18 AM 'Bill Wendling' via Clang Built Linux
> > > wrote:
> > > >
> > > > From:
skb_cache and skb_count fields are used to store skbuff_heads queued
for freeing to flush them by bulks, and aren't related to allocation
path. Give them more obvious names to improve code understanding and
allow to expand this struct with more allocation-related elements.
Misc: indent struct
On 09/01/21 12:31, Greg KH wrote:
Also considering that there will not be more than one copy of this device
(it doesn't make sense as they would all do exactly the same thing), in this
case a module parameter really seems to be the simplest way to configure it.
So you never can have more than
On Mon, Jan 11, 2021 at 10:03:18AM -0800, Randy Dunlap wrote:
> On 1/11/21 9:57 AM, Vanshidhar Konda wrote:
> > On Mon, Jan 11, 2021 at 10:56:36AM +, Will Deacon wrote:
> >> On Sat, Jan 09, 2021 at 09:36:15PM -0800,
> >> vanshiko...@os.amperecomputing.com wrote:
> >>> From: Vanshidhar Konda
Inspired by cpu_map_kthread_run() and _kfree_skb_defer() logics.
Currently, all sorts of skb allocation always do allocate
skbuff_heads one by one via kmem_cache_alloc().
On the other hand, we have percpu napi_alloc_cache to store
skbuff_heads queued up for freeing and flush them by bulks.
We
On Wed, Jan 6, 2021 at 3:07 AM Kirill Tkhai wrote:
>
> On 06.01.2021 01:58, Yang Shi wrote:
> > Currently the number of deferred objects are per shrinker, but some slabs,
> > for example,
> > vfs inode/dentry cache are per memcg, this would result in poor isolation
> > among memcgs.
> >
> > The
On Mon, Jan 11, 2021 at 10:03:18AM -0800, Randy Dunlap wrote:
[EXTERNAL EMAIL NOTICE: This email originated from an external sender. Please
be mindful of safe email handling and proprietary information protection
practices.]
On 1/11/21 9:57 AM, Vanshidhar Konda wrote:
On Mon, Jan 11, 2021
On Mon 11 Jan 09:16 CST 2021, Vinod Koul wrote:
> This add the device node for gpi dma0 instances found in sdm845.
I think the 0 in "dma0" should go?
Apart from that, this looks good.
>
> Signed-off-by: Vinod Koul
> ---
> arch/arm64/boot/dts/qcom/sdm845.dtsi | 46
I'm sending a gentle ping for the below patch.
Especially I'm wondering whether the way how tcmu_destroy_device()
now 'stops' the uio device is ok. Should we better have something
like uio_stop_device() instead?
Thank you,
Bodo
On 18.12.20 15:15, Bodo Stroesser wrote:
tcmu calls
On Mon, Jan 11, 2021 at 08:43:15AM -0800, Tom Rix wrote:
>
> On 1/11/21 8:09 AM, Greg KH wrote:
> > On Mon, Jan 11, 2021 at 07:55:24AM -0800, Tom Rix wrote:
> >> On 1/11/21 6:54 AM, Greg KH wrote:
> >>> On Mon, Jan 11, 2021 at 06:40:24AM -0800, Tom Rix wrote:
> On 1/10/21 10:57 PM, Greg KH
Salut Paul,
Just a minor comment about the v4l2 async API.
On Thu, 31 Dec 2020 at 11:30, Paul Kocialkowski
wrote:
>
> The A31 MIPI CSI-2 controller is a dedicated MIPI CSI-2 bridge
> found on Allwinner SoCs such as the A31 and V3/V3s.
>
> It is a standalone block, connected to the CSI
Some subsystems only have bare tracepoints (a tracepoint with no
associated trace event) to avoid the problem of trace events being an
ABI that can't be changed.
>From bpf presepective, bare tracepoints are what it calls
RAW_TRACEPOINT().
Since bpf assumed there's 1:1 mapping, it relied on
Add some missing glue logic to teach bpf about bare tracepoints - tracepoints
without any trace event associated with them.
Bare tracepoints are declare with DECLARE_TRACE(). Full tracepoints are declare
with TRACE_EVENT().
BPF can attach to these tracepoints as RAW_TRACEPOINT() only as there's
Reuse module_attach infrastructure to add a new bare tracepoint to check
we can attach to it as a raw tracepoint.
Signed-off-by: Qais Yousef
---
Andrii
I was getting the error below when I was trying to run the test.
I had to comment out all related fentry* code to be able to test the raw_tp
On Mon, Jan 11, 2021 at 07:11:25PM +0100, Greg KH wrote:
> On Mon, Jan 11, 2021 at 05:35:00PM +, Matthew Wilcox wrote:
> > On Mon, Jan 11, 2021 at 06:05:13PM +0100, Christoph Hellwig wrote:
> > > None of the complicated overlapping regions bits of the kobj_map are
> > > required for the
On Wed, Jan 6, 2021 at 3:39 AM Kirill Tkhai wrote:
>
> On 06.01.2021 01:58, Yang Shi wrote:
> > The following patch is going to add nr_deferred into shrinker_map, the
> > change will
> > make shrinker_map not only include map anymore, so rename it to a more
> > general
> > name. And this
On Wed, Jan 6, 2021 at 2:22 AM Kirill Tkhai wrote:
>
> On 06.01.2021 01:58, Yang Shi wrote:
> > Currently registered shrinker is indicated by non-NULL
> > shrinker->nr_deferred.
> > This approach is fine with nr_deferred at the shrinker level, but the
> > following
> > patches will move
quote ends without a blank line; unexpected unindent.
Rectify ReST formatting in ./Documentation/fpga/dfl.rst.
Signed-off-by: Lukas Bulwahn
Acked-by: Moritz Fischer
Acked-by: Matthew Gerlach
---
applies cleanly on next-20210111
Moritz, Matthew, please ack.
Greg, please pick this doc fixup to
Hi Leo,
Suzuki and Mike have pointed out a few things to modify and there was a couple
of kernel bot warnings to address as well. As such I will wait for your next
revision before looking at this set.
Thanks,
Mathieu
On Sat, Jan 09, 2021 at 03:44:28PM +0800, Leo Yan wrote:
> This patch series
[Resending the last message] Happy 2021 everyone!
> Dear all:
>
> Hope you are all well.
>
> Sagi and I were wondering if you have any additional feedback on the
> updated patch? (@Ming?) We have been receiving a lot of
> interest/questions from industry on incorporation of i10 in the
> kernel.
Hi,
so there's a breakage of a use case with gdbserver on fsgsbase machines,
see
https://sourceware.org/bugzilla/show_bug.cgi?id=26804
Tom has an even simpler reproducer:
$ cat test.c
int
main (void)
{
return 0;
}
$ gcc test.c -m32
$ gdbserver localhost:12345 a.out
... other terminal ...
$
On Mon 11 Jan 09:16 CST 2021, Vinod Koul wrote:
> This adds capability to use GSI DMA for I2C transfers
>
> Signed-off-by: Vinod Koul
> ---
> drivers/i2c/busses/i2c-qcom-geni.c | 246 -
> 1 file changed, 244 insertions(+), 2 deletions(-)
>
> diff --git
On Mon, Jan 11, 2021 at 05:34:57PM +0100, Lukas Bulwahn wrote:
> On Mon, Jan 11, 2021 at 4:52 PM Greg Kroah-Hartman
> wrote:
> >
> > On Mon, Jan 11, 2021 at 12:21:13PM +0100, Lukas Bulwahn wrote:
> > > Commit fa41d10589be ("fpga: dfl-pci: locate DFLs by PCIe vendor specific
> > > capability")
On 1/10/21 4:10 AM, Thorsten Leemhuis wrote:
> * About 66 of those ~200 components will assign bugs to email addresses
> that look valid, but 125 of them end with @kernel-bugs.osdl.org or
> @kernel-bugs.kernel.org. Those domains do not exist anymore, mails
> sent there bounce ('Unrouteable
On 12/24/2020 3:05 AM, leonid.rav...@dell.com wrote:
From: Leonid Ravich
to remove locking from nvmet_fc_find_target_queue
which called per IO.
Signed-off-by: Leonid Ravich
---
drivers/nvme/target/fc.c | 54
1 file changed, 32
Hi Ricardo,
Thanks a lot for doing this media-wide cleanup.
Aside from a silly typo here in the commit title, s/sum4i-csi/sun4i-csi,
all the patches seem fine.
Thanks,
Ezequiel
On Mon, 11 Jan 2021 at 11:56, Ricardo Ribalda wrote:
>
> Core code already clears reserved fields of struct
>
On Mon, Jan 11, 2021 at 05:35:00PM +, Matthew Wilcox wrote:
> On Mon, Jan 11, 2021 at 06:05:13PM +0100, Christoph Hellwig wrote:
> > None of the complicated overlapping regions bits of the kobj_map are
> > required for the character device lookup, so just a trivial xarray
> > instead.
>
>
* Axel Rasmussen (axelrasmus...@google.com) wrote:
> On Mon, Jan 11, 2021 at 3:58 AM Dr. David Alan Gilbert
> wrote:
> >
> > * Axel Rasmussen (axelrasmus...@google.com) wrote:
> > > This feature allows userspace to intercept "minor" faults. By "minor"
> > > fault, I mean the following situation:
On Mon, Jan 11, 2021 at 06:05:13PM +0100, Christoph Hellwig wrote:
> None of the complicated overlapping regions bits of the kobj_map are
> required for the character device lookup, so just a trivial xarray
> instead.
>
> Signed-off-by: Christoph Hellwig
Thanks for doing this!
Reviewed-by:
On Fri, Jan 8, 2021 at 3:13 AM Tom Rix wrote:
>
>
> On 1/7/21 12:41 PM, Jason Gunthorpe wrote:
> > On Tue, Dec 29, 2020 at 06:46:53PM -0800, t...@redhat.com wrote:
> >> From: Tom Rix
> >>
> >> In ocrdma_dealloc_ucontext_pd() uctx->cntxt_pd is assigned to
> >> the variable pd and then after
On Mon, Jan 11, 2021 at 06:16:39PM +0100, Peter Zijlstra wrote:
>
> While thinking more about this, I'm thinking a big part of the problem
> is that we're not dinstinguishing between geniuine per-cpu kthreads and
> kthreads that just happen to be per-cpu.
>
> Geniuine per-cpu kthreads are
Hi Geert,
On Mon, Jan 11, 2021 at 10:02 AM Geert Uytterhoeven
wrote:
>
> As nwl_dsi.lanes is u32, and NSEC_PER_SEC is 10L, the second
> multiplication in
>
> dsi->lanes * 8 * NSEC_PER_SEC
>
> will overflow on a 32-bit platform. Fix this by making the constant
> unsigned long long,
On Mon, Jan 11, 2021, Tom Lendacky wrote:
> On 1/8/21 6:47 PM, Sean Christopherson wrote:
> > Free sev_asid_bitmap if the reclaim bitmap allocation fails, othwerise
> > it will be leaked as sev_hardware_teardown() frees the bitmaps if and
> > only if SEV is fully enabled (which obviously isn't the
On Fri, 11 Dec 2020 at 02:20, Andre Przywara wrote:
>
> From: Yangtao Li
>
> This patch adds support for A100 MMC controller, which use word address
> for internal dma.
>
> Signed-off-by: Yangtao Li
> Signed-off-by: Andre Przywara
Applied for next to my mmc tree, thanks!
Kind regards
Uffe
On Mon, 14 Dec 2020 at 18:23, Douglas Anderson wrote:
>
> The MSM SDHCI driver always set the "actual_clock" field to 0. It had
> a comment about it not being needed because we weren't using the
> standard SDHCI divider mechanism and we'd just fallback to
> "host->clock". However, it's still
On Tue, 29 Dec 2020 at 09:19, Jisheng Zhang wrote:
>
> Commit a44f7cb93732 ("mmc: core: use mrq->sbc when sending CMD23 for
> RPMB") began to use ACMD23 for RPMB if the host supports ACMD23. In
> RPMB ACM23 case, we need to set bit 31 to CMD23 argument, otherwise
> RPMB write operation will
On Fri, 11 Dec 2020 at 02:20, Andre Przywara wrote:
>
> From: Yangtao Li
>
> Add binding for A100's and H616's mmc and emmc controller.
>
> Signed-off-by: Yangtao Li
> Signed-off-by: Andre Przywara
Applied for next to my mmc tree, thanks!
Kind regards
Uffe
> ---
>
On Mon, 14 Dec 2020 at 18:23, Douglas Anderson wrote:
>
> As talked about in commit 5e4b7e82d497 ("clk: qcom: gcc-sdm845: Use
> floor ops for sdcc clks"), most clocks handled by the Qualcomm clock
> drivers are rounded _up_ by default instead of down. We should make
> sure SD/MMC clocks are
On Fri, 11 Dec 2020 at 15:17, Marcin Wojtas wrote:
>
> From: Alex Leibovich
>
> Automatic Clock Gating is a feature used for the power
> consumption optimisation. It turned out that
> during early init phase it may prevent the stable voltage
> switch to 1.8V - due to that on some platfroms an
After commit da5fb18225b4 ("bpf: Support pre-2.25-binutils objcopy for
vmlinux BTF"), having CONFIG_DEBUG_INFO_BTF enabled but lacking a valid
copy of pahole results in a kernel that will fully compile but fail to
link. The user then has to either install pahole or disable
CONFIG_DEBUG_INFO_BTF
On Thu, 10 Dec 2020 at 09:55, Jisheng Zhang wrote:
>
> The SDHCI_PRESET_FOR_* registers are not set(all read as zeros), so
> set the quirk.
>
> Signed-off-by: Jisheng Zhang
Applied for next, thanks!
Kind regards
Uffe
> ---
> drivers/mmc/host/sdhci-of-dwcmshc.c | 1 +
> 1 file changed, 1
On Thu, 17 Dec 2020 at 21:42, Christophe JAILLET
wrote:
>
> 'sdhci_remove_host()' and 'sdhci_pltfm_free()' should be used in place of
> 'mmc_remove_host()' and 'mmc_free_host()'.
>
> This avoids some resource leaks, is more in line with the error handling
> path of the probe function, and is more
On Thu, 17 Dec 2020 at 22:09, Christophe JAILLET
wrote:
>
> A call to 'ausdhi6_dma_release()' to undo a previous call to
> 'usdhi6_dma_request()' is missing in the error handling path of the probe
> function.
>
> It is already present in the remove function.
>
> Fixes: 75fa9ea6e3c0 ("mmc: add a
On Tue, 8 Dec 2020 at 21:35, Christophe JAILLET
wrote:
>
> If 'mmc_of_parse()' fails, we must undo the previous 'dma_request_chan()'
> call.
>
> Fixes: abd37cccd47f ("mmc: mxs: use mmc_gpio_get_ro for detecting read-only
> status")
> Signed-off-by: Christophe JAILLET
Applied for next (by
On Wed, 9 Dec 2020 at 20:42, Christophe JAILLET
wrote:
>
> 'dma_request_chan()' calls should be balanced by a corresponding
> 'dma_release_channel()' call.
>
> Add the missing call both in the error handling path of the probe function
> and in the remove function.
>
> Fixes: ff65ffe46d28 ("mmc:
> On 2021-01-11 15:43, Marc Orr wrote:
minus sta...@vger.kernel.org, per gregkh@'s email.
> > diff --git a/kernel/dma/direct.c b/kernel/dma/direct.c
> > index 0a4881e59aa7..3d9b17fe5771 100644
> > --- a/kernel/dma/direct.c
> > +++ b/kernel/dma/direct.c
> > @@ -374,9 +374,11 @@ void
On Mon, Jan 11, 2021 at 06:24:35PM +0100, David Hildenbrand wrote:
> On 11.01.21 17:33, Wesley Zhao wrote:
> > From: "Wesley.Zhao"
> >
> > For now "reserve=" is limitied to 32bit,not available on 64bit
> > platform,so we change the get_option() to get_option_ull(added in
> > patch: commit
On 1/11/21 9:57 AM, Vanshidhar Konda wrote:
> On Mon, Jan 11, 2021 at 10:56:36AM +, Will Deacon wrote:
>> On Sat, Jan 09, 2021 at 09:36:15PM -0800, vanshiko...@os.amperecomputing.com
>> wrote:
>>> From: Vanshidhar Konda
>>>
>>> Increase the default value of NR_CPUS to 512 from 256. This will
On Mon, 11 Jan 2021 at 18:28, Jakub Kicinski wrote:
>
> On Mon, 11 Jan 2021 18:16:17 +0100 Loic Poulain wrote:
> > From: Hemant Kumar
> >
> > Introduce mhi_get_free_desc_count() API to return number
> > of TREs available to queue buffer. MHI clients can use this
> > API to know before hand if
On Mon, Jan 11, 2021 at 05:37:36PM +, Colin Ian King wrote:
> On 11/01/2021 16:35, Mark Brown wrote:
> > This doesn't apply against current code, please check and resend.
> ..both set ret to non-zero, which I believe will throw a subsequent
> warning messagethat's not strictly related.
> my
On Mon, Jan 11, 2021, Tom Lendacky wrote:
> On 1/11/21 10:02 AM, Tom Lendacky wrote:
> > On 1/8/21 6:47 PM, Sean Christopherson wrote:
> > > Use "guest" instead of "enabled" for the global "running as an SEV guest"
> > > flag to avoid confusion over whether "sev_enabled" refers to the guest or
> >
On Mon, Jan 11, 2021 at 10:56:36AM +, Will Deacon wrote:
On Sat, Jan 09, 2021 at 09:36:15PM -0800, vanshiko...@os.amperecomputing.com
wrote:
From: Vanshidhar Konda
Increase the default value of NR_CPUS to 512 from 256. This will
enable the defconfig kernel to support platforms that have
On 1/8/21 6:47 PM, Sean Christopherson wrote:
> Replace calls to svm_sev_enabled() with direct checks on sev_enabled, or
> in the case of svm_mem_enc_op, simply drop the call to svm_sev_enabled().
> This effectively replaces checks against a valid max_sev_asid with checks
> against sev_enabled.
On Tue, Dec 29, 2020 at 01:30:31PM -0800, Yu-cheng Yu wrote:
> @@ -895,6 +903,12 @@ static void init_speculation_control(struct cpuinfo_x86
> *c)
> }
> }
>
> +static void init_cet_features(struct cpuinfo_x86 *c)
> +{
> + if (cpu_has(c, X86_FEATURE_SHSTK) || cpu_has(c,
On 1/10/21 3:46 PM, Sam Ravnborg wrote:
> Hi all,
>> Hi Arnd!
>>
>> (Please let's have this cross-posted for more visibility. I only learned
>> about this
>> while reading Phoronix news)
>>
>>> I also looked at non-ARM platforms while preparing for my article. Some of
>>> these look like they
On 11-01-21, 08:47, Doug Anderson wrote:
> Hi,
>
> On Mon, Jan 11, 2021 at 7:18 AM Vinod Koul wrote:
> >
> > @@ -2622,6 +2626,13 @@ pinmux {
> >"gpio2", "gpio3";
> > function = "qup0";
> >
On 1/6/21 8:09 PM, Christoph Lameter wrote:
> On Wed, 6 Jan 2021, Vlastimil Babka wrote:
>
>> rather accept some wasted memory in scenarios that should be rare anyway
>> (full
>> memory hot remove), as we do the same in other contexts already. It's all RFC
>> for now, as I might have missed
On Mon, 11 Jan 2021, Greg Kroah-Hartman wrote:
> From: Linus Torvalds
>
> commit c2407cf7d22d0c0d94cf20342b3b8f06f1d904e7 upstream.
>
> Ever since commit 2a9127fcf229 ("mm: rewrite wait_on_page_bit_common()
> logic") we've had some very occasional reports of BUG_ON(PageWriteback)
> in
Il 10/01/21 20:35, Linus Walleij ha scritto:
On Sun, Jan 10, 2021 at 3:32 PM AngeloGioacchino Del Regno
wrote:
So, I've retried some basic usage of the regcache, relevant snippets here:
static bool aw9523_volatile_reg(struct device *dev, unsigned int reg)
{
return reg ==
On Mon, Jan 11, 2021 at 05:44:17PM +, John Garry wrote:
> On 11/01/2021 17:41, Ahmed S. Darwish wrote:
> > On Tue, Jan 12, 2021 at 01:28:32AM +0800, John Garry wrote:
> > ...
> > > index a920eced92ec..6a51abdc59ae 100644
> > > --- a/drivers/scsi/mvsas/mv_sas.c
> > > +++
On Mon, Jan 11, 2021 at 06:19:26PM +0100, Christoph Hellwig wrote:
> sizeof needs to be called on the compat pointer, not the native one.
>
> Fixes: 89cd35c58bc2 ("iov_iter: transparently handle compat iovecs in
> import_iovec")
> Reported-by: David Laight
> Signed-off-by: Christoph Hellwig
On Fri, Jan 8, 2021 at 5:09 AM Walter Wu wrote:
>
> CONFIG_KASAN_STACK and CONFIG_KASAN_STACK_ENABLE both enable KASAN stack
> instrumentation, but we should only need one config, so that we remove
> CONFIG_KASAN_STACK_ENABLE and make CONFIG_KASAN_STACK workable. see [1].
>
> When enable KASAN
On 1/8/21 3:19 PM, Song Liu wrote:
Replace hashtab with task local storage in runqslower. This improves the
performance of these BPF programs. The following table summarizes average
runtime of these programs, in nanoseconds:
task-local hash-prealloc
On 11.01.21 16:17, Max Krummenacher wrote:
> When the kernel is configured to use the Thumb-2 instruction set
> "suspend-to-memory" fails to resume. Observed on a Colibri iMX6ULL
> (i.MX 6ULL) and Apalis iMX6 (i.MX 6Q).
>
> It looks like the CPU resumes unconditionally in ARM instruction mode
On Mon, Jan 11, 2021 at 10:06:43AM -0500, Qian Cai wrote:
> On Sun, 2021-01-10 at 17:39 +0200, Mike Rapoport wrote:
> > On Wed, Jan 06, 2021 at 04:04:21PM -0500, Qian Cai wrote:
> > > On Wed, 2021-01-06 at 10:05 +0200, Mike Rapoport wrote:
> > > > I think we trigger PF_POISONED_CHECK() in
Hi Konrad,
On 11-01-21, 17:04, Konrad Dybcio wrote:
> Hi,
>
> looks like sdm845-cheza also uses the spi0 bus, which as far as I
> understand is going to break with the GPI DMA disabled. Perhaps it
> should also be enabled over there?
If it is working without GPI enabled, it would work.. GPI for
From: Giulio Benetti
During commit 88bc4178568b ("drm: Use new
DRM_BUS_FLAG_*_(DRIVE|SAMPLE)_(POS|NEG)EDGE flags") DRM_BUS_FLAG_*
macros have been changed to avoid ambiguity but just because of this
ambiguity previous DRM_BUS_FLAG_PIXDATA_(POS/NEG)EDGE were used meaning
_SAMPLE_ not _DRIVE_.
On Mon, Jan 11, 2021 at 6:31 PM Yonghong Song wrote:
>
>
>
> On 1/8/21 3:19 PM, Song Liu wrote:
> > Task local storage is enabled for tracing programs. Add a test for it
> > without CONFIG_BPF_LSM.
Can you also explain what the test does in the commit log?
It would also be nicer to have a
On 11/01/2021 17:41, Ahmed S. Darwish wrote:
On Tue, Jan 12, 2021 at 01:28:32AM +0800, John Garry wrote:
...
index a920eced92ec..6a51abdc59ae 100644
--- a/drivers/scsi/mvsas/mv_sas.c
+++ b/drivers/scsi/mvsas/mv_sas.c
@@ -230,7 +230,7 @@ static void mvs_bytes_dmaed(struct mvs_info *mvi, int i)
On 11-01-21, 09:34, Bjorn Andersson wrote:
> On Mon 11 Jan 09:16 CST 2021, Vinod Koul wrote:
>
> > I2C geni driver needs to access struct geni_wrapper, so move it to
> > header.
> >
>
> Please tell me more!
>
> Glanced through the other patches and the only user I can find it in
> patch 5
On Wed, Jan 6, 2021 at 2:16 AM Kirill Tkhai wrote:
>
> On 06.01.2021 01:58, Yang Shi wrote:
> > Both memcg_shrinker_map_size and shrinker_nr_max is maintained, but
> > actually the
> > map size can be calculated via shrinker_nr_max, so it seems unnecessary to
> > keep both.
> > Remove
On Mon, 11 Jan 2021, Thierry Reding wrote:
> On Sun, Jan 10, 2021 at 08:44:13PM -0800, Hugh Dickins wrote:
> >
> > Synaptics RMI4 SMBus touchpad on ThinkPad X1 Carbon (5th generation)
> > fails to suspend when running 5.11-rc kernels: bisected to
> > 5b6164d3465f ("driver core: Reorder devices
On Tue, Jan 12, 2021 at 01:28:32AM +0800, John Garry wrote:
...
> index a920eced92ec..6a51abdc59ae 100644
> --- a/drivers/scsi/mvsas/mv_sas.c
> +++ b/drivers/scsi/mvsas/mv_sas.c
> @@ -230,7 +230,7 @@ static void mvs_bytes_dmaed(struct mvs_info *mvi, int i)
> }
>
> sas_ha = mvi->sas;
>
On Fri, Jan 8, 2021 at 9:31 PM Arnd Bergmann wrote:
>
> On Fri, Jan 8, 2021 at 7:56 PM Andrey Konovalov wrote:
> > On Fri, Jan 8, 2021 at 5:09 AM Walter Wu wrote:
>
> > > @@ -2,6 +2,12 @@
> > > CFLAGS_KASAN_NOSANITIZE := -fno-builtin
> > > KASAN_SHADOW_OFFSET ?= $(CONFIG_KASAN_SHADOW_OFFSET)
Marc Gonzalez writes:
> [ Dropping maintainers of other platforms ]
>
> On 08/01/2021 23:55, Arnd Bergmann wrote:
>
>> After v5.10 was officially declared an LTS kernel, I had a look around
>> the Arm platforms that look like they have not seen any patches from
>> their maintainers or users that
On Mon, Jan 11, 2021 at 5:20 PM Max Krummenacher wrote:
>
> When the kernel is configured to use the Thumb-2 instruction set
> "suspend-to-memory" fails to resume. Observed on a Colibri iMX6ULL
> (i.MX 6ULL) and Apalis iMX6 (i.MX 6Q).
>
> It looks like the CPU resumes unconditionally in ARM
On 1/11/21 4:09 AM, Dmitry Osipenko wrote:
11.01.2021 14:50, Dmitry Osipenko пишет:
20.10.2020 19:37, Sowjanya Komatineni пишет:
On 10/20/20 12:48 AM, Thierry Reding wrote:
On Mon, Oct 19, 2020 at 09:03:54PM -0700, Sowjanya Komatineni wrote:
VI I2C don't have DMA support and uses PIO mode
On 1/8/21 3:19 PM, Song Liu wrote:
Update the Makefile to prefer using ../../../vmlinux, which has latest
definitions for vmlinux.h
Signed-off-by: Song Liu
---
tools/bpf/runqslower/Makefile | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
701 - 800 of 2008 matches
Mail list logo
