On 2021-01-29, Nick Desaulniers wrote:
On Fri, Jan 29, 2021 at 12:11 PM Nathan Chancellor wrote:
clang produces .eh_frame sections when CONFIG_GCOV_KERNEL is enabled,
even when -fno-asynchronous-unwind-tables is in KBUILD_CFLAGS:
$ make CC=clang vmlinux
...
ld: warning: orphan section
On Wed, Jan 27, 2021 at 09:44:28AM +0100, Arnaud POULIQUEN wrote:
> Hi Mathieu,
>
> Come back on you series...
>
> On 12/18/20 6:32 PM, Mathieu Poirier wrote:
> > Add an new get_loaded_rsc_table() operation in order to support
> > scenarios where the remoteproc core has booted a remote processor
On Fri, Jan 29, 2021 at 1:11 PM Jakub Jelinek wrote:
>
> On Fri, Jan 29, 2021 at 01:05:56PM -0800, Nick Desaulniers wrote:
> > > Wasn't that fixed in GAS?
> > > https://sourceware.org/bugzilla/show_bug.cgi?id=27195
> >
> > $ make LLVM=1 -j72 defconfig
> > $ ./scripts/config -e DEBUG_INFO -e
Correct compile issue if CONFIG_TTY is not set by
only adding ttyVK devices if CONFIG_TTY is set.
Reported-by: Randy Dunlap
Signed-off-by: Scott Branden
---
Changes since v1:
Add function stubs rather than compiling out code
---
drivers/misc/bcm-vk/Makefile | 4 ++--
Hi!
> > Motorola is using a custom TS 27.010 based serial port line discipline
>
> s/serial port line discipline/multiplexer protocol/
> > diff --git a/drivers/gnss/Kconfig b/drivers/gnss/Kconfig
> > index bd12e3d57baa..a7c449d8428c 100644
> > --- a/drivers/gnss/Kconfig
> > +++
On 1/29/2021 1:00 PM, Dave Hansen wrote:
On 1/27/21 1:25 PM, Yu-cheng Yu wrote:
@@ -135,6 +135,8 @@ enum xfeature {
#define XFEATURE_MASK_PT (1 << XFEATURE_PT_UNIMPLEMENTED_SO_FAR)
#define XFEATURE_MASK_PKRU(1 << XFEATURE_PKRU)
#define XFEATURE_MASK_PASID
On Fri, Jan 29, 2021 at 6:03 PM Sven Van Asbroeck wrote:
>
> Hoi Willem, thanks a lot for reviewing this patch, much appreciated !!
>
> On Fri, Jan 29, 2021 at 5:11 PM Willem de Bruijn
> wrote:
> >
> > > +static struct sk_buff *
> > > +lan743x_rx_trim_skb(struct sk_buff *skb, int frame_length)
>
Lubomir Rintel writes:
> Lines ending with obscenely long URLs at the end don't look good.
>
> Even if these links are not that long at this point, they will be when
> replaced with an archive link in a subsequent patch -- let's prepare for
> that.
>
> Signed-off-by: Lubomir Rintel
> ---
>
In order to solidify support for a reasonable set of commands a set of
relatively safe commands are added and thus nullifying the need to use
raw operations to access them.
Signed-off-by: Ben Widawsky
---
drivers/cxl/mem.c| 8
include/uapi/linux/cxl_mem.h | 4
2 files
Currently, when handling the SPMI summary interrupt, the hw_irq
number is calculated based on SID, Peripheral ID, IRQ index and
APID. This is then passed to irq_find_mapping() to see if a
mapping exists for this hw_irq and if available, invoke the
interrupt handler. Since the IRQ index uses an
Can,
> The initialization of clk_scaling.min_gear was removed by mistake. This
> change adds it back, otherwise clock scaling down would fail.
Applied to 5.12/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
Clang's integrated assembler only accepts UAL syntax, rewrite the
instructions that were changed by RVCTv2.1.
The document "Assembly language changes after RVCTv2.1" was very
helpful.
This exposed a bug in Clang's integrated assembler, which hopefully will
land in clang-12, but is required to
Lukas,
> Commit 0653c358d2dc ("scsi: Drop gdth driver") misses to adjust MAINTAINERS.
>
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains:
>
> warning: no file matches F:drivers/scsi/gdt*
Applied to 5.12/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux
On Fri, Jan 29, 2021 at 1:13 AM 'Michal Hocko' via kernel-team
wrote:
>
> On Thu 28-01-21 23:03:40, Suren Baghdasaryan wrote:
> > Initial version of process_madvise(2) manual page. Initial text was
> > extracted from [1], amended after fix [2] and more details added using
> > man pages of
From: Hangbin Liu
commit 2efdaaaf883a143061296467913c01aa1ff4b3ce upstream.
Based on RFC 8200, Section 4.5 Fragment Header:
- If the first fragment does not include all headers through an
Upper-Layer header, then that fragment should be discarded and
an ICMP Parameter Problem,
On Fri, 29 Jan 2021 at 16:47, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.4.94 release.
> There are 18 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.
>
>
On Fri, Jan 29, 2021 at 8:43 PM Nick Desaulniers
wrote:
>
> DWARF v5 is the latest standard of the DWARF debug info format.
>
> Feature detection of DWARF5 is onerous, especially given that we've
> removed $(AS), so we must query $(CC) for DWARF5 assembler directive
> support.
>
> The DWARF
On 1/29/2021 12:46 PM, Borislav Petkov wrote:
On Fri, Jan 29, 2021 at 12:33:43PM -0800, Dave Hansen wrote:
In that case is there any reason to keep the "depends on CPU_SUP_INTEL"?
Probably not. I haven't heard of the AMD implementation being somehow
different from Intel's.
Ok, I will
On Thu, Jan 28, 2021 at 04:56:26PM -0800, Marc MERLIN wrote:
> On Wed, Jan 27, 2021 at 03:33:00PM -0600, Bjorn Helgaas wrote:
> > Hi Marc, I appreciate your persistence on this. I am frankly
> > surprised that you've put up with this so long.
>
> Well, been using linux for 27 years, but also
On Fri, Jan 29, 2021 at 1:11 PM Andy Shevchenko
wrote:
>
> On Fri, Jan 29, 2021 at 10:49 PM Yury Norov wrote:
> >
> > Many algorithms become simplier if they are passed with relatively small
>
> simpler
>
> > input values. One example is bitmap operations when the whole bitmap fits
> > into one
On Wed, Jan 27, 2021 at 12:15 PM Kees Cook wrote:
>
> On Mon, Jan 25, 2021 at 01:45:25PM +0100, Arnd Bergmann wrote:
> > From: Arnd Bergmann
> >
> > I ran into a couple of problems with kunit tests taking too much stack
> > space, sometimes dangerously so. These the the three instances that
> >
Christoph Hellwig writes:
> On Thu, Jan 28, 2021 at 05:50:56PM -0300, Thiago Jung Bauermann wrote:
>> > struct module *find_module(const char *name)
>> > {
>> > - module_assert_mutex();
>>
>> Does it make sense to replace the assert above with the warn below
>> (untested)?
>>
>>
On Fri, Jan 29, 2021 at 06:45:21AM +0300, Dmitry Baryshkov wrote:
> On 28/01/2021 22:26, Rob Herring wrote:
> > On Thu, Jan 28, 2021 at 11:52 AM Dmitry Baryshkov
> > wrote:
> > >
> > > Some Qualcomm platforms require to power up an external device before
> > > probing the PCI bus. E.g. on RB5
On 2021-01-29, Nick Desaulniers wrote:
DWARF v5 is the latest standard of the DWARF debug info format.
Feature detection of DWARF5 is onerous, especially given that we've
removed $(AS), so we must query $(CC) for DWARF5 assembler directive
support.
The DWARF version of a binary can be
On Fri, Jan 29, 2021 at 07:29:31PM +0100, Jan Henrik Weinstock wrote:
> This patch proposes to use the device tree to determine the present cpus
> instead of assuming all CONFIG_NRCPUS are actually present in the system.
>
> Signed-off-by: Jan Henrik Weinstock
> ---
> arch/openrisc/kernel/smp.c
Hi Andrew, thank you so much for looking at this patch !
On Fri, Jan 29, 2021 at 3:36 PM Andrew Lunn wrote:
>
> So this patch appears to contain two different changes
> 1) You only allocate a receive buffer as big as the MTU plus overheads
> 2) You change the cache operations to operate on the
On Mon, Jan 25, 2021 at 09:18:46AM -0800, Guenter Roeck wrote:
> Hi Lukasz,
>
> On Sat, Jan 23, 2021 at 02:42:47AM +0100, Lukasz Majczak wrote:
> > There is a missing call to start_tpm_chip before the call to
> > the tpm_get_timeouts() and tpm_tis_probe_irq_single(). As the current
> > approach
On Fri, Jan 29, 2021 at 6:08 PM Willem de Bruijn
wrote:
>
> Okay. I found it a bit hard to parse how much true code change was
> mixed in with just reindenting existing code. If a lot, then no need
> to split of the code refactor.
Thank you. The code is quite hard to review in patch format.
The Get Log command returns the actual log entries that are advertised
via the Get Supported Logs command (0400h). CXL device logs are selected
by UUID which is part of the CXL spec. Because the driver tries to
sanitize what is sent to hardware, there becomes a need to restrict the
types of logs
clang produces .eh_frame sections when CONFIG_GCOV_KERNEL is enabled,
even when -fno-asynchronous-unwind-tables is in KBUILD_CFLAGS:
$ make CC=clang vmlinux
...
ld: warning: orphan section `.eh_frame' from `init/main.o' being placed in
section `.eh_frame'
ld: warning: orphan section `.eh_frame'
On Fri, Jan 29, 2021 at 07:26:06PM +0100, m...@richard-neumann.de wrote:
> From: Richard Neumann
>
> The macro work_amd_i2c_common is not used anywhere in the driver.
> Removed it.
After addressing Subject as per comment against the previous patch, feel free
to add
Reviewed-by: Andy Shevchenko
The conversion to regmap introduced a regression at the code
which reads from the IRQ register. Address that.
Fixes: 8148fe6afb24 ("staging: hikey9xx: spmi driver: convert to regmap")
Signed-off-by: Mauro Carvalho Chehab
---
drivers/staging/hikey9xx/hi6421-spmi-pmic.c | 2 +-
1 file changed, 1
On Thu, Jan 28, 2021 at 6:26 PM Daniel Latypov wrote:
>
> Currently, given something (fairly dystopian) like
> > KUNIT_EXPECT_EQ(test, 2 + 2, 5)
>
> KUnit will prints a failure message like this.
> > Expected 2 + 2 == 5, but
> > 2 + 2 == 4
> > 5 == 5
>
> With this patch, the output
On 1/29/21 12:02 PM, Jakub Kicinski wrote:
On Fri, 29 Jan 2021 11:48:15 -0800 Shoaib Rao wrote:
SO_OOBINLINE does not control the delivery of signal, It controls how
OOB Byte is delivered. It may not be obvious but this change does not
deliver any Byte, just a signal. So, as long as sendmsg
If an error occurs starting a channel, don't "thaw" it.
We should assume the channel remains in a non-started state.
Update the comment in gsi_channel_stop(); calls to this function are
no longer retried.
Signed-off-by: Alex Elder
---
drivers/net/ipa/gsi.c | 6 --
1 file changed, 4
On 1/29/21 11:32 AM, Srinivas Kandagatla wrote:
Add support to new interrupts and update irq routine in a way
to deal with multiple pending interrupts with in a single interrupt!
I can't parse the wording after 'update irq routine'.
+ swrm->reg_write(swrm, SWRM_INTERRUPT_CLEAR,
Open-code gsi_channel_freeze() and gsi_channel_thaw() in all callers
and get rid of these two functions. This is part of reworking the
sequence of things done during channel suspend/resume and start/stop.
Signed-off-by: Alex Elder
---
drivers/net/ipa/gsi.c | 37
Create a new function that does most of the work of starting a
channel. What's different is that it takes a flag indicating
whether the channel should really be stopped or not. When doing a
"normal" channel start, the flag is true. Create another new
function __gsi_channel_stop() that behaves
> diff --git a/drivers/net/ethernet/microchip/lan743x_main.c
> b/drivers/net/ethernet/microchip/lan743x_main.c
> index f1f6eba4ace4..f485320e5784 100644
> --- a/drivers/net/ethernet/microchip/lan743x_main.c
> +++ b/drivers/net/ethernet/microchip/lan743x_main.c
> @@ -1957,11 +1957,11 @@ static int
On Fri, Jan 29, 2021 at 12:45 PM Yury Norov wrote:
>
> Bitmap operations are much simpler and faster in case of small bitmaps, whicn
> fit into a single word. In linux/bitmap.h we have a machinery that allows
> compiler to replace actual function call with a few instructions if bitmaps
> passed
On 1/29/21 12:44 PM, Shoaib Rao wrote:
On 1/29/21 12:18 PM, Jakub Kicinski wrote:
On Fri, 29 Jan 2021 12:10:21 -0800 Shoaib Rao wrote:
On 1/29/21 12:02 PM, Jakub Kicinski wrote:
On Fri, 29 Jan 2021 11:48:15 -0800 Shoaib Rao wrote:
Data was discarded because the flag was not supported,
On Sat, Jan 30, 2021 at 5:31 AM Nathan Chancellor wrote:
>
> On Wed, Jan 13, 2021 at 05:34:47PM -0700, Nathan Chancellor wrote:
> > The most common question around building the Linux kernel with clang is
> > "does it work?" and the answer has always been "it depends on your
> > architecture,
On Thu, Jan 28, 2021 at 11:43 PM Sedat Dilek wrote:
>
> Some comments:
>
> [ hash mismatches ]
>
> Observed identical warnings when doing a rebuild with GAS or Clang-IAS.
>
> [ Importance of LLVM_IAS=1 working ]
>
> Clang-LTO and Clang-CFI depend both on LLVM_IAS=1 (see for example
> "kbuild: add
On Fri, Jan 29, 2021 at 1:20 PM Sedat Dilek wrote:
>
> On Fri, Jan 29, 2021 at 10:13 PM Sedat Dilek wrote:
> >
> > On Fri, Jan 29, 2021 at 10:09 PM Nick Desaulniers
> > wrote:
> > >
> > > On Fri, Jan 29, 2021 at 12:55 PM Sedat Dilek
> > > wrote:
> > > >
> > > > On Fri, Jan 29, 2021 at 9:48 PM
On Fri, Jan 29, 2021 at 11:03 AM Catalin Marinas
wrote:
>
> arm64 fixes:
>
> - Fix the virt_addr_valid() returning true for < PAGE_OFFSET addresses.
That's a really odd fix.
It went from an incorrect bitwise operation (masking) to an _odd_
bitwise operation (xor).
Yes, PAGE_OFFSET has the bit
Joel,
Can you ack this patch?
-- Steve
On Thu, 28 Jan 2021 09:35:13 +0800
Song Chen wrote:
> The kernel thread executing test can run on any cpu, which might be
> different cpu latency tracer is running on, as a result, the
> big latency caused by preemptirq delay test can't be detected.
>
On Fri, Jan 29, 2021 at 11:21 PM Nick Desaulniers
wrote:
>
> On Fri, Jan 29, 2021 at 2:11 PM Sedat Dilek wrote:
> >
> > On Fri, Jan 29, 2021 at 11:09 PM Nick Desaulniers
> > wrote:
> > >
> > > On Fri, Jan 29, 2021 at 1:20 PM Sedat Dilek wrote:
> > > >
> > > > On Fri, Jan 29, 2021 at 10:13 PM
On Thu, Jan 28, 2021 at 02:59:13PM -0800, Axel Rasmussen wrote:
> > +pte_t *huge_pte_alloc(struct mm_struct *mm, structt vm_area_struct *vma,
>
> This was pointed out to me just after I sent v3 of my series today
> (which includes this patch):
>
> Typo, s/structt/struct/.
Thanks Axel - fixed
On Wed, Jan 27, 2021 at 09:50:31AM +0100, Arnaud POULIQUEN wrote:
>
>
> On 12/18/20 6:32 PM, Mathieu Poirier wrote:
> > Introduce function rproc_detach() to enable the remoteproc
> > core to release the resources associated with a remote processor
> > without stopping its operation.
> >
> >
On Fri, Jan 29, 2021 at 2:23 PM Sedat Dilek wrote:
>
> On Fri, Jan 29, 2021 at 11:21 PM Nick Desaulniers
> wrote:
> >
> > On Fri, Jan 29, 2021 at 2:11 PM Sedat Dilek wrote:
> > >
> > > On Fri, Jan 29, 2021 at 11:09 PM Nick Desaulniers
> > > wrote:
> > > >
> > > > On Fri, Jan 29, 2021 at 1:20
On Fri, Jan 29, 2021 at 5:01 PM Jakub Kicinski wrote:
>
> You may need to rebase to see this:
>
> drivers/net/ethernet/microchip/lan743x_main.c:2123:41: warning: restricted
> __le32 degrades to integer
Good catch. The problem goes away with the next commit in the set.
This is probably because I
On 2021-01-29, Nick Desaulniers wrote:
DWARF v5 is the latest standard of the DWARF debug info format.
Feature detection of DWARF5 is onerous, especially given that we've
removed $(AS), so we must query $(CC) for DWARF5 assembler directive
support.
The DWARF version of a binary can be
On Fri, Jan 29, 2021 at 3:25 PM Nick Desaulniers
wrote:
>
> On Fri, Jan 29, 2021 at 2:10 PM Jakub Jelinek wrote:
> >
> > On Fri, Jan 29, 2021 at 02:05:59PM -0800, Nick Desaulniers wrote:
> > > Ah, I see. Then I should update the script I add
> > > (scripts/test_dwarf5_support.sh) to feature
On Thu, Jan 28, 2021 at 11:17:16AM -0800, Eric Anholt wrote:
> On Thu, Jan 28, 2021 at 10:52 AM Jordan Crouse wrote:
> >
> > On Wed, Jan 27, 2021 at 03:39:44PM -0800, Eric Anholt wrote:
> > > We were using the same force-poweron bit in the two codepaths, so they
> > > could race to have one of
> I'd encourage anyone thinking about "using OOB" to read
> https://tools.ietf.org/html/rfc6093 first. Basically, TCP does not
> actually provide an OOB mechanism, and frankly Unix sockets shouldn't
> try either.
OOB data maps much better onto ISO transport 'expedited data'
than anything in a
All the necessary bits are initialized in order to find and map the
register space for CXL Memory Devices. This is accomplished by using the
Register Locator DVSEC (CXL 2.0 - 8.1.9.1) to determine which PCI BAR to
use, and how much of an offset from that BAR should be added.
If the memory device
On Fri, Jan 29, 2021 at 4:08 PM Sedat Dilek wrote:
>
> On Fri, Jan 29, 2021 at 8:43 PM Nick Desaulniers
> wrote:
> >
> > DWARF v5 is the latest standard of the DWARF debug info format.
> >
> > DWARF5 wins significantly in terms of size and especially so when mixed
> > with compression
Hi,
I'm not sure the first post of this pull request made it through so
sending again.
A few more fixes for a late rc:
- fix lockdep complaint on 32bit arches and also remove an unsafe memory
use due to device vs filesystem lifetime
- two fixes for free space tree
- race during log replay
Hi,
please consider applying the patches chained to this message.
The objective is to deal with the a large amount of dead links to
material that often comes handy in marvel.rst; and improve some details
along the way.
Thank you
Lubo
This company is not the superheroes you're looking for.
Signed-off-by: Lubomir Rintel
---
Documentation/arm/{marvel.rst => marvell.rst} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename Documentation/arm/{marvel.rst => marvell.rst} (100%)
diff --git a/Documentation/arm/marvel.rst
Just remove these; there's good chance there wasn't anything useful
there anyway.
Signed-off-by: Lubomir Rintel
---
Documentation/arm/marvel.rst | 27 ++-
1 file changed, 2 insertions(+), 25 deletions(-)
diff --git a/Documentation/arm/marvel.rst
Good morning,
On Wed, Jan 27, 2021 at 05:53:50PM +, Mike Leach wrote:
> The current fixed metadata version format (version 0), means that adding
> metadata parameter items renders files from a previous version of perf
> unreadable. Per CPU parameters appear in a fixed order, but there is no
>
Lines ending with obscenely long URLs at the end don't look good.
Even if these links are not that long at this point, they will be when
replaced with an archive link in a subsequent patch -- let's prepare for
that.
Signed-off-by: Lubomir Rintel
---
Documentation/arm/marvel.rst | 209
Marvell has an annoying habit of moving stuff around their web site
every full moon, and often just removing documents altogether.
At this point basically none but four of the links still works and even
those that work today weren't working for a long period of time
previously. That is a shame
MMP2 is used in XO-1.75 and MMP3 is now supported in mainline.
Signed-off-by: Lubomir Rintel
---
Documentation/arm/marvel.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/arm/marvel.rst b/Documentation/arm/marvel.rst
index 0c291d1091f1d..43f2fe407796e
This patchset implements the asynchronous mode support for ARMv8.5-A
Memory Tagging Extension (MTE), which is a debugging feature that allows
to detect with the help of the architecture the C and C++ programmatic
memory errors like buffer overflow, use-after-free, use-after-return, etc.
MTE is
Architectures supported by KASAN_HW_TAGS can provide a sync or async mode
of execution. On an MTE enabled arm64 hw for example this can be identified
with the synchronous or asynchronous tagging mode of execution.
In synchronous mode, an exception is triggered if a tag check fault occurs.
In
MTE provides a mode that asynchronously updates the TFSR_EL1 register
when a tag check exception is detected.
To take advantage of this mode the kernel has to verify the status of
the register at:
1. Context switching
2. Return to user/EL0 (Not required in entry from EL0 since the kernel
On Wed, Jan 27, 2021 at 6:41 PM Uwe Kleine-König wrote:
>
> The driver core ignores the return value of struct bus_type::remove()
> because there is only little that can be done. To simplify the quest to
> make this function return void, let struct vio_driver::remove() return
> void, too. All
On Fri, Jan 29 2021 at 10:08, Peter Zijlstra wrote:
> On Fri, Jan 29, 2021 at 12:28:41AM +0100, Thomas Gleixner wrote:
>
>> Add a test case which covers this scenario. This is modeled after the
>> WINE testcase, but changes the expect in step #2 to:
>>
>>- Expect DR6::BS == 1 and DR6::BR0 ==
moyufeng wrote:
>Ping...
>Any comments? Thanks!
>
>On 2021/1/15 10:02, moyufeng wrote:
>> Hi Team,
>>
>> I have a question about bonding. During testing bonding mode 4
>> scenarios, I find that there is a very low probability that
>> the pointer is null. The following information is displayed:
On Fri, Jan 29, 2021 at 2:06 PM Pavel Tatashin
wrote:
>
> > > Definitely, but we should try figuring out what's going on here. I
> > > assume on x86-64 it behaves differently?
> >
> > Yes, we should root cause. I highly suspect that there is somewhere
> > alignment miscalculations happen that
From: Sven Van Asbroeck
Multi-buffer packets enable us to use rx ring buffers smaller than
the mtu. This will allow us to change the mtu on-the-fly, without
having to stop the network interface in order to re-size the rx
ring buffers.
This is a big change touching a key driver function
Move the calls to enable or disable IEOB interrupts out of
__gsi_channel_start() and __gsi_channel_stop() and into their
callers. This is a small step to make the next patch easier
to understand.
Signed-off-by: Alex Elder
---
drivers/net/ipa/gsi.c | 45
No completion interrupts will occur while an endpoint is suspended,
or when a channel has been stopped for suspend. So there's no need
to disable the interrupt during suspend and re-enable it when
resuming.
We'll enable the interrupt when we first start the channel, and
disable it again only
The channel stop and suspend paths both call __gsi_channel_stop(),
which quiesces channel activity, disables NAPI, and (on other than
SDM845) stops the channel. Similarly, the start and resume paths
share __gsi_channel_start(), which starts the channel and re-enables
NAPI again.
Disabling NAPI
Disable the I/O completion interrupt on a channel *after* we
successfully stop it rather than before. This ensures a completion
occurring just before the channel is stopped triggers an interrupt.
Enable the interrupt *before* starting a channel rather than after,
to be symmetric. A stopped
Bitmap operations are much simpler and faster in case of small bitmaps, whicn
fit into a single word. In linux/bitmap.h we have a machinery that allows
compiler to replace actual function call with a few instructions if bitmaps
passed into the function is small and its size is known at compile
On 1/27/21 1:25 PM, Yu-cheng Yu wrote:
> @@ -135,6 +135,8 @@ enum xfeature {
> #define XFEATURE_MASK_PT (1 << XFEATURE_PT_UNIMPLEMENTED_SO_FAR)
> #define XFEATURE_MASK_PKRU (1 << XFEATURE_PKRU)
> #define XFEATURE_MASK_PASID (1 << XFEATURE_PASID)
> +#define
Hi,
On 1/29/21 9:28 PM, Linus Torvalds wrote:
> On Fri, Jan 29, 2021 at 12:02 PM Linus Torvalds
> wrote:
>>
>> It's fairly easy to work around in this in the tty layer by just
>> avoiding that function entirely, so I'll cook up a patch to do that.
>> But I'm adding the appropriate people to the
On Fri, Jan 29, 2021 at 10:49 PM Yury Norov wrote:
>
> Many algorithms become simplier if they are passed with relatively small
simpler
> input values. One example is bitmap operations when the whole bitmap fits
> into one word. To implement such simplifications, linux/bitmap.h declares
>
On Fri, Jan 29, 2021 at 10:54 PM Yury Norov wrote:
> On Fri, Jan 29, 2021 at 12:45 PM Yury Norov wrote:
> >
> > Bitmap operations are much simpler and faster in case of small bitmaps,
> > whicn
> > fit into a single word. In linux/bitmap.h we have a machinery that allows
> > compiler to replace
On Fri, Jan 29, 2021 at 01:05:56PM -0800, Nick Desaulniers wrote:
> > Wasn't that fixed in GAS?
> > https://sourceware.org/bugzilla/show_bug.cgi?id=27195
>
> $ make LLVM=1 -j72 defconfig
> $ ./scripts/config -e DEBUG_INFO -e DEBUG_INFO_DWARF5
> $ make LLVM=1 -j72
> ...
> /tmp/init-d50d89.s:
On Fri, Jan 29, 2021 at 05:57:17PM +0100, Rafael J. Wysocki wrote:
> On Fri, Jan 29, 2021 at 5:45 PM Sakari Ailus
> wrote:
> >
> > Hi Rafael,
> >
> > Thanks for the comments.
> >
> > On Fri, Jan 29, 2021 at 03:07:57PM +0100, Rafael J. Wysocki wrote:
> > > On Fri, Jan 29, 2021 at 12:27 AM Sakari
Hi Clemens,
On Fri, Jan 29, 2021 at 3:37 PM Clemens Gruber
wrote:
>
> Is the driver really responsible for bootloaders that program the chip
> with invalid values?
No, but it's responsible for correcting invalid values. Otherwise the driver
doesn't work.
> The chip comes out of PoR with sane
On Fri, 2021-01-29 at 23:10 +0200, Andy Shevchenko wrote:
> On Fri, Jan 29, 2021 at 10:49 PM Yury Norov wrote:
[]
> > @@ -37,7 +37,7 @@
> > #define GENMASK(h, l) \
> > (GENMASK_INPUT_CHECK(h, l) + __GENMASK(h, l))
> >
> > -#define BITS_FIRST(nr) GENMASK(nr), 0)
> > +#define
On Fri, 29 Jan 2021 14:01:03 -0500
Steven Rostedt wrote:
> On Fri, 29 Jan 2021 18:59:43 +0100
> Peter Zijlstra wrote:
>
> > On Fri, Jan 29, 2021 at 09:45:48AM -0800, Alexei Starovoitov wrote:
> > > Same things apply to bpf side. We can statically prove safety for
> > > ftrace and kprobe
Hi Clemens,
On Fri, Jan 29, 2021 at 4:24 PM Sven Van Asbroeck wrote:
>
> LEN_ON = 409, LED_OFF = 1228 and
> LED_ON = 419, LED_OFF = 1238
> produce the same result. you can't see the difference between the two
> when scoping the channel. there are probably more ways to do this,
> some might
On Fri, Jan 29, 2021 at 1:11 PM Jakub Jelinek wrote:
>
> On Fri, Jan 29, 2021 at 01:05:56PM -0800, Nick Desaulniers wrote:
> > > Wasn't that fixed in GAS?
> > > https://sourceware.org/bugzilla/show_bug.cgi?id=27195
> >
> > $ make LLVM=1 -j72 defconfig
> > $ ./scripts/config -e DEBUG_INFO -e
On Sat, Jan 30, 2021 at 01:19:10AM +0300, Dmitry Baryshkov wrote:
> On Sat, 30 Jan 2021 at 00:50, Bjorn Helgaas wrote:
> > On Fri, Jan 29, 2021 at 06:45:21AM +0300, Dmitry Baryshkov wrote:
> > > On 28/01/2021 22:26, Rob Herring wrote:
> > > > On Thu, Jan 28, 2021 at 11:52 AM Dmitry Baryshkov
> >
Thanks for the explanation and test code. I think I see better what
is going on here.
[I took your idea for using madvise(...MADV_HWPOISON) and added a new "-S"
option to my einj_mem_uc test program to use madvise instead of ACPI/EINJ
for injections. Update pushed here:
Hoi Willem, thanks a lot for reviewing this patch, much appreciated !!
On Fri, Jan 29, 2021 at 5:11 PM Willem de Bruijn
wrote:
>
> > +static struct sk_buff *
> > +lan743x_rx_trim_skb(struct sk_buff *skb, int frame_length)
> > +{
> > + if (skb_linearize(skb)) {
>
> Is this needed? That will
On 1/29/21 2:49 PM, Jarkko Sakkinen wrote:
> On Mon, Jan 25, 2021 at 09:18:46AM -0800, Guenter Roeck wrote:
>> Hi Lukasz,
>>
>> On Sat, Jan 23, 2021 at 02:42:47AM +0100, Lukasz Majczak wrote:
>>> There is a missing call to start_tpm_chip before the call to
>>> the tpm_get_timeouts() and
On Fri, Jan 29, 2021 at 8:43 PM Nick Desaulniers
wrote:
>
> DWARF v5 is the latest standard of the DWARF debug info format.
>
> DWARF5 wins significantly in terms of size and especially so when mixed
> with compression (CONFIG_DEBUG_INFO_COMPRESSED).
>
> Link:
allmodconfig
powerpc allnoconfig
i386 randconfig-a001-20210129
i386 randconfig-a002-20210129
i386 randconfig-a004-20210129
i386 randconfig-a005-20210129
i386 randconfig-a003-20210129
i386
DWARF v5 is the latest standard of the DWARF debug info format.
DWARF5 wins significantly in terms of size and especially so when mixed
with compression (CONFIG_DEBUG_INFO_COMPRESSED).
Link: http://www.dwarfstd.org/doc/DWARF5.pdf
Patch 1 is a cleanup that lays the ground work and isn't DWARF
v5
On 2021/1/30 1:03, Robin Murphy wrote:
> On 2021-01-29 15:34, John Garry wrote:
>> On 29/01/2021 15:12, Robin Murphy wrote:
>>> On 2021-01-27 11:32, Zhen Lei wrote:
The MODULE_SOFTDEP() gives user space a hint of the loading sequence. And
when command "modprobe arm_smmuv3_pmu" is
On Fri, Jan 29, 2021 at 05:11:53PM -0600, Eric W. Biederman wrote:
> "Serge E. Hallyn" writes:
>
> > On Thu, Jan 28, 2021 at 08:44:26PM +0100, Miklos Szeredi wrote:
> >> On Thu, Jan 28, 2021 at 6:09 PM Serge E. Hallyn wrote:
> >> >
> >> > On Tue, Jan 19, 2021 at 07:34:49PM -0600, Eric W.
From: Mark Gross
The Intel Vision Processing Unit (VPU) is an IP block that is showing up for
the first time as part of the Keem Bay SOC. Keem Bay is a quad core A53 Arm
SOC. It is designed to be used as a stand alone SOC as well as in an PCIe
Vision Processing accelerator add in card.
This
From: Srikanth Thokala
Add Synopsys PCIe DWC core embedded-DMA functionality for local host
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
Reviewed-by: Mark Gross
Signed-off-by: Srikanth Thokala
---
drivers/misc/xlink-pcie/local_host/Makefile | 1 +
drivers/misc/xlink-pcie/local_host/dma.c
201 - 300 of 532 matches
Mail list logo
