On Thu, May 14, 2020 at 02:51:01PM -0400, Sasha Levin wrote:
> From: Christian Gromm
>
> [ Upstream commit 5e56bc06e18dfc8a66180fa369384b36e2ab621a ]
>
> This patch replaces function module_init() with subsys_initcall().
> It is needed to ensure that the core module of the driver is
> initialize
Perf's expr code currently builds an array of strings then removes
duplicates. The array is larger than necessary and has recently been
increased in size. When this was done it was commented that a hashmap
would be preferable.
libbpf has a hashmap but libbpf isn't currently required to build
perf.
Fixes the following warnings:
hashmap.c: In function ‘hashmap__clear’:
hashmap.h:150:20: error: comparison of integer expressions of different
signedness: ‘int’ and ‘size_t’ {aka ‘long unsigned int’} [-Werror=sign-compare]
150 | for (bkt = 0; bkt < map->cap; bkt++)\
hashmap.c: In func
Allow use of hashmap in more than just libbpf, where it isn't an
exported symbol. Place in libapi as that is a required part of
tools/perf whereas libbpf is currently optional.
Modify perf's check-headers.sh script to check that the files are kept
in sync, in the same way kernel headers are checked
Break pmu-events test into 2 and add a test to verify that all pmu
metric expressions simply parse. Try to parse all metric ids/events,
skip/warn if metrics for the current architecture fail to parse. To
support warning for a skip, and an ability for a subtest to describe why
it skips.
Tested on p
Remove #include of libbpf_internal.h that is unused.
Discussed in this thread:
https://lore.kernel.org/lkml/caef4bzzrmieds_8r8g4vaaewvjzpb4xylnpf0x2vny8otzk...@mail.gmail.com/
Signed-off-by: Ian Rogers
---
tools/lib/bpf/hashmap.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/tools/lib/bpf/h
Use a hashmap between a char* string and a double* value. While bpf's
hashmap entries are size_t in size, we can't guarantee sizeof(size_t) >=
sizeof(double). Avoid a memory allocation when gathering ids by making 0.0
a special value encoded as NULL.
Original map suggestion by Andi Kleen:
https://
Now subtests can inform why a test was skipped. The upcoming patch
improvint PMU event metric testing will use it.
Signed-off-by: Ian Rogers
Cc: Adrian Hunter
Cc: Alexander Shishkin
Cc: Andi Kleen
Cc: Jin Yao
Cc: Jiri Olsa
Cc: John Garry
Cc: Kajol Jain
Cc: Kan Liang
Cc: Leo Yan
Cc: Mark
From: Andrii Nakryiko
Fix memory leak in hashmap_clear() not freeing hashmap_entry structs for each
of the remaining entries. Also NULL-out bucket list to prevent possible
double-free between hashmap__clear() and hashmap__free().
Running test_progs-asan flavor clearly showed this problem.
Repor
Localize the hashmap__* symbols in libbpf.a. To allow for a version in
libapi.
Before:
$ nm libbpf.a
...
0002088a t hashmap_add_entry
0001712a t hashmap__append
00020aa3 T hashmap__capacity
0002099c T hashmap__clear
000208b3 t hashmap_del_entry
00020
Hi Mason,
On 15/05/20 10:26AM, masonccy...@mxic.com.tw wrote:
>
> Hi Pratyush,
>
> > > > > I can't apply your patches to enable xSPI Octal mode for
> > > > > mx25uw51245g because your patches set up Octal protocol first and
> > > > > then using Octal protocol to write Configuration Register 2(
Hi Kunihiko,
I love your patch! Perhaps something to improve:
[auto build test WARNING on pci/next]
[also build test WARNING on robh/for-next v5.7-rc5 next-20200514]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use
On 2020/5/15 12:19, Matthew Wilcox wrote:
> On Thu, May 07, 2020 at 03:50:57PM +0800, Zhen Lei wrote:
>> +++ b/block/blk-settings.c
>> @@ -150,7 +150,7 @@ void blk_queue_max_hw_sectors(struct request_queue *q,
>> unsigned int max_hw_secto
>> unsigned int max_sectors;
>>
>> if ((max_
On 15.5.2020 8.45, jiahao wrote:
> It is obvious that XCHI_MAX_HALT_USEC is usec,
> not milliseconds; Replace 'milliseconds' with
> 'usec' of the debug message.
>
> Signed-off-by: jiahao
> ---
> drivers/usb/host/xhci.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/dr
Hi Rik,
Commit 145f573b89a62 ("Make lazy TLB mode lazier").
A couple of questions here (and I don't know the x86 architecture too
well let alone the ASID stuff, so bear with me). I'm assuming, and it
appears to be in the x86 manual that you can't map the same physical
page with conflicting mem
On Tue, May 12, 2020 at 6:56 PM Neil Armstrong wrote:
>
> This Microcontroller is present on the Khadas VIM1, VIM2, VIM3 and Edge
> boards.
>
> It has multiple boot control features like password check, power-on
> options, power-off control and system FAN control on recent boards.
>
> Signed-off-b
On 2020/5/15 12:14, Matthew Wilcox wrote:
> On Thu, May 07, 2020 at 03:50:56PM +0800, Zhen Lei wrote:
>> +++ b/mm/page_io.c
>> @@ -38,7 +38,7 @@ static struct bio *get_swap_bio(gfp_t gfp_flags,
>>
>> bio->bi_iter.bi_sector = map_swap_page(page, &bdev);
>> bio_set_dev(
+CC: fstests
On Thu, May 14, 2020 at 4:15 PM Jeff Layton wrote:
>
> On Thu, 2020-05-14 at 13:48 +0100, Luis Henriques wrote:
> > On Thu, May 14, 2020 at 08:10:09AM -0400, Jeff Layton wrote:
> > > On Thu, 2020-05-14 at 12:14 +0100, Luis Henriques wrote:
> > > > Similarly to commit 03f219041fdb ("c
On Tue, May 12, 2020 at 6:56 PM Neil Armstrong wrote:
>
> The new Khadas VIM2 and VIM3 boards controls the cooling fan via the
> on-board microcontroller.
>
> This implements the FAN control as thermal devices and as cell of the Khadas
> MCU MFD driver.
>
> Signed-off-by: Neil Armstrong
> ---
>
On 12-05-20, 22:12, Andy Shevchenko wrote:
> On Tue, May 12, 2020 at 05:08:20PM +0300, Serge Semin wrote:
> > On Fri, May 08, 2020 at 02:41:53PM +0300, Andy Shevchenko wrote:
> > > On Fri, May 08, 2020 at 01:53:03PM +0300, Serge Semin wrote:
> > > > IP core of the DW DMA controller may be synthesiz
On Thu, May 14, 2020 at 06:43:06PM -0600, Jeffrey Hugo wrote:
> On 5/14/2020 8:07 AM, Jeffrey Hugo wrote:
> > +#define QAIC_NAME "Qualcomm Cloud AI 100"
>
> > +static struct pci_driver qaic_pci_driver = {
> > + .name = QAIC_NAME,
>
> A question about the community's preference
On Thu, May 14, 2020 at 05:53:55PM -0700, David Miller wrote:
> You're not undoing one, but two levels of abstraction here.
>
> Is this "ipip6_tunnel_locate()" call part of the SIT ioctl implementation?
Yes. Take a look at the convoluted case handling the
SIOCADDTUNNEL and SIOCCHGTUNNEL commands
Hi Serge,
On 12-05-20, 15:42, Serge Semin wrote:
> Vinod,
>
> Could you join the discussion for a little bit?
>
> In order to properly fix the problem discussed in this topic, we need to
> introduce an additional capability exported by DMA channel handlers on
> per-channel
> basis. It must be a
Hi,
Georgi Djakov writes:
>> Sandeep Maheswaram writes:
>>> +static int dwc3_qcom_interconnect_init(struct dwc3_qcom *qcom)
>>> +{
>>> + struct device *dev = qcom->dev;
>>> + int ret;
>>> +
>>> + if (!device_is_bound(&qcom->dwc3->dev))
>>> +
On 2020/5/15 10:15, Jaegeuk Kim wrote:
> Let's guarantee flusing dirty meta pages to avoid infinite loop.
What's the root cause? Race case or meta page flush failure?
Thanks,
>
> Signed-off-by: Jaegeuk Kim
> ---
> fs/f2fs/checkpoint.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(
On 2020/5/15 12:06, Matthew Wilcox wrote:
> On Thu, May 07, 2020 at 03:50:56PM +0800, Zhen Lei wrote:
>> @@ -266,7 +266,7 @@ int swap_writepage(struct page *page, struct
>> writeback_control *wbc)
>>
>> static sector_t swap_page_sector(struct page *page)
>> {
>> -return (sector_t)__page
Add dwcmshc specific system-level suspend and resume support.
Signed-off-by: Jisheng Zhang
---
drivers/mmc/host/sdhci-of-dwcmshc.c | 43 +
1 file changed, 43 insertions(+)
diff --git a/drivers/mmc/host/sdhci-of-dwcmshc.c
b/drivers/mmc/host/sdhci-of-dwcmshc.c
index a
Change since v7:
- specify compatible property as const string
- add maxItem in required property
- squash keypad example nodes
- sort header file with alphabetic order
- align all define values and add MTK_ prefix to make more uniform
- change debounce value to default 16ms if not specified in dt
On Tue, May 05, 2020 at 03:53:45PM +0200, Arnd Bergmann wrote:
> When building for ARMv7-M, clang-9 or higher tries to unroll some loops,
> which ends up confusing the register allocator to the point of generating
> rather bad code and using more than the warning limit for stack frames:
>
> warnin
On Sat, May 09, 2020 at 12:34:58AM +0200, Rikard Falkeborn wrote:
> A small series constifying struct debugfs_reg32 where it can be made
> const. There's no dependency between the patches.
>
> Rikard Falkeborn (4):
> crypto: ccree - constify struct debugfs_reg32
> crypto: hisilicon/hpre - cons
This patch allows users to swap the Fn and left Control keys on all Apple
keyboards: internal (e.g. Macbooks) and external (both wired and wireless).
The patch adds a new hid-apple module param: swap_fn_leftctrl (off by default).
Signed-off-by: Zakhar Semenov
---
This patch was created to elimin
On 12-05-20, 15:35, Andy Shevchenko wrote:
> On Tue, May 12, 2020 at 12:16:22AM +0300, Serge Semin wrote:
> > On Fri, May 08, 2020 at 02:21:52PM +0300, Andy Shevchenko wrote:
> > > On Fri, May 08, 2020 at 01:53:01PM +0300, Serge Semin wrote:
> > > > Maximum block size DW DMAC configuration correspo
Hey Linus,
As mentioned last week an i915 PR came in late, but I left it, so the
i915 bits of this cover 2 weeks, which is why it's likely a bit larger
than usual. Otherwise it's mostly amdgpu fixes, one tegra fix, one
meson fix.
Regards,
Dave.
drm-fixes-2020-05-15:
drm fixes for v5.7-rc6
i915
Hi,
On 5/15/20 08:54, Felipe Balbi wrote:
>
> Hi,
>
> Georgi Djakov writes:
>> On 5/14/20 20:13, Matthias Kaehlcke wrote:
>>> On Thu, May 14, 2020 at 02:30:28PM +0300, Felipe Balbi wrote:
Felipe Balbi writes:
> Hi,
>
> Sandeep Maheswaram writes:
>> +static int dwc3_q
On 12-05-20, 15:38, Andy Shevchenko wrote:
> On Tue, May 12, 2020 at 02:49:46PM +0300, Serge Semin wrote:
> > On Tue, May 12, 2020 at 12:08:04PM +0300, Andy Shevchenko wrote:
> > > On Tue, May 12, 2020 at 12:35:31AM +0300, Serge Semin wrote:
> > > > On Tue, May 12, 2020 at 12:01:38AM +0300, Andy Sh
Gustavo A. R. Silva wrote:
> The current codebase makes use of the zero-length array language
> extension to the C90 standard, but the preferred mechanism to declare
> variable-length types such as these ones is a flexible array member[1][2],
> introduced in C99:
>
> struct foo {
>int stu
Hi Jiri,
On 5/9/2020 3:37 PM, Jin, Yao wrote:
Hi Jiri,
On 5/5/2020 8:03 AM, Jiri Olsa wrote:
On Sat, May 02, 2020 at 10:33:59AM +0800, Jin, Yao wrote:
SNIP
@@ -1461,6 +1461,9 @@ static int get_group_fd(struct evsel *evsel, int cpu, int
thread)
BUG_ON(!leader->core.fd);
fd = F
Hi all,
After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
arch/x86/kernel/ftrace.c: In function 'set_ftrace_ops_ro':
arch/x86/kernel/ftrace.c:444:32: error: 'ftrace_epilogue' undeclared (first use
in this function)
444 |end_offset = (unsigned long
On Thu, 14 May 2020 12:18:58 +0200 Ulf Hansson wrote:
>
>
> On Thu, 14 May 2020 at 07:45, Jisheng Zhang
> wrote:
> >
> > On Wed, 13 May 2020 14:15:21 +0200 Ulf Hansson wrote:
> >
> > >
> > >
> > > On Wed, 13 May 2020 at 11:47, Jisheng Zhang
> > > wrote:
> > > >
> > > > This reverts commi
On 04/15/20 at 02:04pm, Kristen Carlson Accardi wrote:
...
> diff --git a/arch/x86/boot/compressed/misc.c b/arch/x86/boot/compressed/misc.c
> index 9652d5c2afda..2e108fdc7757 100644
> --- a/arch/x86/boot/compressed/misc.c
> +++ b/arch/x86/boot/compressed/misc.c
> @@ -26,9 +26,6 @@
> * it is not s
Hi,
Georgi Djakov writes:
> On 5/14/20 20:13, Matthias Kaehlcke wrote:
>> On Thu, May 14, 2020 at 02:30:28PM +0300, Felipe Balbi wrote:
>>> Felipe Balbi writes:
>>>
Hi,
Sandeep Maheswaram writes:
> +static int dwc3_qcom_interconnect_init(struct dwc3_qcom *qcom)
> +{
On Tue, May 5, 2020 at 7:16 AM Thomas Gleixner wrote:
>
> irq_enter()/exit() include the RCU handling. To properly separate the RCU
> handling provide variants which contain only the non-RCU related
> functionality.
Acked-by: Andy Lutomirski
The ANX7625 is an ultra-low power 4K Mobile HD Transmitter designed
for portable device. It converts MIPI DSI/DPI to DisplayPort 1.3 4K.
The ANX7625 can support both USB Type-C PD feature and MIPI DSI/DPI
to DP feature. This driver only enabled MIPI DSI/DPI to DP feature.
Signed-off-by: Xin Ji
-
On 06-05-20, 12:28, Rafał Hibner wrote:
> List elements are not formally removed from list during zynqmp_dma_reset.
Applied after fixing subsystem name to dmaengine, thanks
--
~Vinod
anx7625: MIPI to DP transmitter DT schema
Signed-off-by: Xin Ji
---
.../bindings/display/bridge/analogix,anx7625.yaml | 95 ++
1 file changed, 95 insertions(+)
create mode 100644
Documentation/devicetree/bindings/display/bridge/analogix,anx7625.yaml
diff --git
a/Document
Hi all,
The following series add support for the Slimport ANX7625 transmitter, a
ultra-low power Full-HD 4K MIPI to DP transmitter designed for portable device.
This is the v11 version, any mistakes, please let me know, I will fix it in
the next series.
Change history:
v11: Fix comments from Ro
Hi Petr,
On Thu, 14 May 2020 at 14:13, Petr Mladek wrote:
>
> On Wed 2020-05-13 19:04:48, Sumit Garg wrote:
> > On Tue, 12 May 2020 at 19:55, Daniel Thompson
> > wrote:
> > >
> > > On Tue, May 12, 2020 at 02:18:34PM +0530, Sumit Garg wrote:
> > > > Since commit 42a0bb3f7138 ("printk/nmi: generic
It is obvious that XCHI_MAX_HALT_USEC is usec,
not milliseconds; Replace 'milliseconds' with
'usec' of the debug message.
Signed-off-by: jiahao
---
drivers/usb/host/xhci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
index
On Tue, May 5, 2020 at 7:16 AM Thomas Gleixner wrote:
>
> Convert #DF to IDTENTRY_DF
> - Implement the C entry point with DEFINE_IDTENTRY_DF
> - Emit the ASM stub with DECLARE_IDTENTRY_DF on 64bit
> - Remove the ASM idtentry in 64bit
> - Adjust the 32bit shim code
> - Fixup the XEN/PV co
On Tue, May 5, 2020 at 7:16 AM Thomas Gleixner wrote:
>
> Provide a separate macro for #DF as this needs to emit paranoid only code
> and has also a special ASM stub in 32bit.
Acked-by: Andy Lutomirski
but... maybe it would be cleaner just to open-code all of this in the
next patch? This is a
On Tue, May 5, 2020 at 7:16 AM Thomas Gleixner wrote:
>
> The functions invoked from handle_debug() can be instrumented. Tell objtool
> about it.
Acked-by: Andy Lutomirski
On Tue, May 5, 2020 at 7:16 AM Thomas Gleixner wrote:
>
> Mark the relevant functions noinstr, use the plain non-instrumented MSR
> accessors. The only odd part is the instr_begin()/end() pair around the
> indirect machine_check_vector() call as objtool can't figure that out. The
> possible invoke
On Tue, May 5, 2020 at 7:16 AM Thomas Gleixner wrote:
>
> Now that there are separate entry points, move the kernel/user_mode specifc
> checks into the entry functions so the common handling code does not need
> the extra mode checks. Make the code more readable while at it.
Acked-by: Andy Lutomi
Hi Rob,
Can you please let us know if you have any inputs on this.
Regards,
Bharat
> -Original Message-
> From: Bharat Kumar Gogada
> Sent: Thursday, May 7, 2020 5:29 PM
> To: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org
> Cc: lorenzo.pieral...@arm.com; bhelg...@google.com; r
On Tue, May 5, 2020 at 7:16 AM Thomas Gleixner wrote:
>
> From: Peter Zijlstra
>
> DR6/7 should be handled before nmi_enter() is invoked and restore after
> nmi_exit() to minimize the exposure.
>
> Split it out into helper inlines and bring it into the correct order.
> +*
> +* En
The amount of time spent parsing fwnodes of devices can become really
high if the devices are added in an non-ideal order. Worst case can be
O(N^2) when N devices are added. But this can be optimized to O(N) by
adding all the devices and then parsing all their fwnodes in one batch.
This commit add
Commit 4dbe191c046e ("driver core: Add device links from fwnode only for
the primary device") skipped linking a fwnode's secondary device to
the suppliers listed in its fwnode.
However, a fwnode's secondary device can't be found using
get_dev_from_fwnode(). So, there's no point in trying to see if
The fw_devlink_pause() and fw_devlink_resume() APIs allow batching the
parsing of the device tree nodes when a lot of devices are added. This
will significantly cut down parsing time (as much a 1 second on some
systems). So, use them when adding devices for all the top level device
tree nodes in a
This commit just moves around code to match the general organization of
the file.
Signed-off-by: Saravana Kannan
---
drivers/base/core.c | 60 ++---
1 file changed, 30 insertions(+), 30 deletions(-)
diff --git a/drivers/base/core.c b/drivers/base/core.c
i
When fw_devlink is enabled on hardware with a large number of device
tree nodes, the initial device addition done in
of_platform_default_populate_init() can be very inefficient. This is
because most devices will fail to find all their suppliers when they are
added and will keep trying to parse thei
Hi Jason,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 1ae7efb388540adc1653a51a3bc3b2c9cef5ec1a
commit: 20c384f1ea1a0bc7320bc445c72dd02d2970d594 vhost: refine vhost and vringh
kconfig
date: 6 weeks ago
reprod
On Tue, May 5, 2020 at 7:16 AM Thomas Gleixner wrote:
>
> The MCE entry point uses the same mechanism as the IST entry point for
> now. For #DB split the inner workings and just keep the ist_enter/exit
> magic in the IST variant. Fixup the ASM code to emit the proper
> noist_##cfunc call.
>
Acke
On Tue, May 5, 2020 at 7:16 AM Thomas Gleixner wrote:
>
> Provide NOIST entry point macros which allows to implement NOIST variants
> of the C entry points. These are invoked when #DB or #MC enter from user
> space. This allows explicit handling of the difference between user mode
> and kernel mod
Adding Ashish.
Regards
Poonam
> -Original Message-
> From: Naresh Kamboju
> Sent: Friday, May 15, 2020 10:57 AM
> To: shiva.linuxwo...@gmail.com; Miquel Raynal ;
> Shivamurthy Shastri
> Cc: Richard Weinberger ; Vignesh Raghavendra
> ; Boris Brezillon ;
> Chuanhong Guo ; Frieder Schrempf
Hi all,
Today's linux-next merge of the devicetree tree got a conflict in:
Documentation/devicetree/bindings/net/qcom,ipa.yaml
between commit:
8456c54408a2 ("dt-bindings: net: add IPA iommus property")
from the net-next tree and commit:
fba5618451d2 ("dt-bindings: Fix incorrect 'reg' pr
On Tue, May 5, 2020 at 7:16 AM Thomas Gleixner wrote:
>
> The C entry points do not expect an error code.
Acked-by: Andy Lutomirski
On Tue, May 5, 2020 at 7:16 AM Thomas Gleixner wrote:
>
> Convert #DB to IDTENTRY_ERRORCODE:
> - Implement the C entry point with DEFINE_IDTENTRY_DB
> - Emit the ASM stub with DECLARE_IDTENTRY
> - Remove the ASM idtentry in 64bit
> - Remove the open coded ASM entry code in 32bit
> - Fixu
On Tue, May 5, 2020 at 7:16 AM Thomas Gleixner wrote:
>
> Mark all functions in the fragile code parts noinstr or force inlining so
> they can't be instrumented.
Acked-by: Andy Lutomirski
On Tue, May 5, 2020 at 7:16 AM Thomas Gleixner wrote:
>
> Convert #NMI to IDTENTRY_NMI:
> - Implement the C entry point with DEFINE_IDTENTRY_NMI
> - Fixup the XEN/PV code
> - Remove the old prototyoes
>
> No functional change.
Acked-by: Andy Lutomirski
On Wed, 11 Mar 2020 at 23:28, wrote:
>
> From: Shivamurthy Shastri
>
> This patchset is for the new series of Micron SPI NAND devices, and the
> following links are their datasheets.
While boot NXP ls2088 device with mainline kernel the following
nand warning noticed. How critical this warning ?
On Tue, May 5, 2020 at 7:16 AM Thomas Gleixner wrote:
>
> XEN/PV has special wrappers for NMI and DB exceptions. They redirect these
> exceptions through regular IDTENTRY points. Provide the necessary IDTENTRY
> macros to make this work
Acked-by: Andy Lutomirski
On Tue, May 5, 2020 at 7:16 AM Thomas Gleixner wrote:
>
> Convert #MC to IDTENTRY_MCE:
> - Implement the C entry points with DEFINE_IDTENTRY_MCE
> - Emit the ASM stub with DECLARE_IDTENTRY_MCE
> - Remove the ASM idtentry in 64bit
> - Remove the open coded ASM entry code in 32bit
> - Fixu
On Tue, May 5, 2020 at 7:16 AM Thomas Gleixner wrote:
>
> mce_check_crashing_cpu() is called right at the entry of the MCE
> handler. It uses mce_rdmsr() and mce_wrmsr() which are wrappers around
> rdmsr() and wrmsr() to handle the MCE error injection mechanism, which is
> pointless in this contex
On Tue, May 5, 2020 at 7:16 AM Thomas Gleixner wrote:
>
> There is no reason to have nmi_enter/exit() in the actual MCE
> handlers. Move it to the entry point. This also covers the until now
> uncovered initial handler which only prints.
Acked-by: Andy Lutomirski
On Thu, May 7, 2020 at 11:44 PM Enric Balletbo i Serra
wrote:
>
> Hi Eizan,
>
> On 7/5/20 13:11, Eizan Miyamoto wrote:
> > On Thu, May 7, 2020 at 2:54 AM Enric Balletbo Serra
> > wrote:
> >>
> >> Hi Eizan,
> >>
> >> Thank you for the patch.
> >>
> >> Missatge de Eizan Miyamoto del dia dc., 6 de
Lockdep is screwed here in next-20200514 due to "BUG: MAX_LOCKDEP_ENTRIES too
low". One of the traces below pointed to this linux-next commit,
8c8e824d4ef0 watch_queue: Introduce a non-repeating system-unique superblock ID
which was accidentally just showed up in next-20200514
From: Sudeep Holla
Hi Rob, Arnd and Jassi,
This stuff has been doing rounds on the mailing list since several years
now with no agreed conclusion by all the parties. And here is another
attempt to get some feedback from everyone involved to close this once
and for ever. Your comments will very m
Hello Uwe,
Gentle reminder to review my replies.
It will help me to push next cleaner patch.
Thanks & Regards,
Sandipan
> -Original Message-
> From: Sandipan Patra
> Sent: Thursday, May 7, 2020 1:40 PM
> To: Uwe Kleine-König
> Cc: Thierry Reding ; robh...@kernel.org; Jonathan
> Hunter
On Thu, May 14, 2020 at 9:30 PM Daniel Vetter wrote:
> On Thu, May 14, 2020 at 05:19:40PM +0900, David Stevens wrote:
> > Sorry for the duplicate reply, didn't notice this until now.
> >
> > > Just storing
> > > the uuid should be doable (assuming this doesn't change during the
> > > lifetime of t
Hi Volodymyr,
On Fri, 15 May 2020 at 06:32, Volodymyr Babchuk wrote:
>
> Hi Sumit,
>
> On Thu, 14 May 2020 at 08:38, Sumit Garg wrote:
> >
> > Hi Volodymyr,
> >
> > On Thu, 14 May 2020 at 06:48, Volodymyr Babchuk
> > wrote:
> > >
> > > Hi Sumit,
> > >
> > > On Wed, 13 May 2020 at 11:24, Sumit
On 5/14/20 9:04 PM, Rob Landley wrote:
> FYI I dug up my old https://lkml.org/lkml/2017/9/13/651 and ported it to
> current, because I needed it for a thing.
>
> From: Rob Landley
>
> Make initramfs honor CONFIG_DEVTMPFS_MOUNT, and move
> /dev/console open after devtmpfs mount.
>
> Add workarou
This series adds some features for UniPhier PCIe host controller.
- Add support for PME and AER invoked by MSI interrupt
- Add iATU register view support for PCIe version >= 4.80
- Add an error message when failing to get phy driver
This adds a new function called by MSI handler in DesignWare PCI
This gets iATU register area from reg property. In Synopsis DWC version
4.80 or later, since iATU register area is separated from core register
area, this area is necessary to get from DT independently.
Signed-off-by: Kunihiko Hayashi
---
drivers/pci/controller/dwc/pcie-uniphier.c | 5 +
1 f
Even if phy driver doesn't probe, the error message can't be
distinguished from other errors. This displays error message
caused by the phy driver explicitly.
Signed-off-by: Kunihiko Hayashi
---
drivers/pci/controller/dwc/pcie-uniphier.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
The misc interrupts consisting of PME, AER, and Link event, is handled
by INTx handler, however, these interrupts should be also handled by
MSI handler.
This adds the function uniphier_pcie_misc_isr() that handles misc
intterupts, which is called from both INTx and MSI handlers.
This function dete
In the dt-bindings, "atu" reg-names is required to get the register space
for iATU in Synopsis DWC version 4.80 or later.
Signed-off-by: Kunihiko Hayashi
---
Documentation/devicetree/bindings/pci/uniphier-pcie.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindi
This adds msi_host_isr() callback function support to describe
SoC-dependent service triggered by MSI.
For example, when AER interrupt is triggered by MSI, the callback function
reads SoC-dependent registers and detects that the interrupt is from AER,
and invoke AER interrupts related to MSI.
Sig
On 9/12/19 19:33, Bjorn Andersson wrote:
> On Thu, Aug 29, 2019 at 1:07 AM Viresh Kumar wrote:
>>
>> Building individual drivers as modules is fine but allowing a core
>> framework to be built as a module makes it really complex and should be
>> avoided.
>>
>> Whatever uses the interconnect core A
From: Ira Weiny
Add a flag to preserve FS_XFLAG_DAX in the ext4 inode.
Set the flag to be user visible and changeable. Set the flag to be
inherited. Allow applications to change the flag at any time.
Finally, on regular files, flag the inode to not be cached to facilitate
changing S_DAX on th
From: Ira Weiny
Enable the same per file DAX support in ext4 as was done for xfs. This series
builds and depends on the V11 series for xfs.[1]
This passes the same xfstests test as XFS.
The only issue is that this modifies the old mount option parsing code rather
than waiting for the new parsi
From: Ira Weiny
Update the document to reflect ext4 and xfs now behave the same.
Reviewed-by: Jan Kara
Signed-off-by: Ira Weiny
---
Changes from RFC:
Update with ext2 text...
---
Documentation/filesystems/dax.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
From: Ira Weiny
We add 'always', 'never', and 'inode' (default). '-o dax' continues to
operate the same which is equivalent to 'always'. This new
functionality is limited to ext4 only.
Specifically we introduce a 2nd DAX mount flag EXT4_MOUNT2_DAX_NEVER and set
it and EXT4_MOUNT_DAX_ALWAYS app
From: Ira Weiny
In prep for the new tri-state mount option which then introduces
EXT4_MOUNT_DAX_NEVER.
Reviewed-by: Jan Kara
Signed-off-by: Ira Weiny
---
Changes:
New patch
---
fs/ext4/ext4.h | 4 ++--
fs/ext4/inode.c | 2 +-
fs/ext4/super.c | 12 ++--
3 files changed, 9 i
From: Ira Weiny
To prevent complications with in memory inodes we only set S_DAX on
inode load. FS_XFLAG_DAX can be changed at any time and S_DAX will
change after inode eviction and reload.
Add init bool to ext4_set_inode_flags() to indicate if the inode is
being newly initialized.
Assert tha
From: Ira Weiny
S_DAX should only be enabled when the underlying block device supports
dax.
Change ext4_should_use_dax() to check for device support prior to the
over riding mount option.
While we are at it change the function to ext4_should_enable_dax() as
this better reflects the ask as well
From: Ira Weiny
Encryption and DAX are incompatible. Changing the DAX mode due to a
change in Encryption mode is wrong without a corresponding
address_space_operations update.
Make the 2 options mutually exclusive by returning an error if DAX was
set first.
Furthermore, clarify the documentati
From: Ira Weiny
When preventing DAX and journaling on an inode. Use the effective DAX
check rather than the mount option.
This will be required to support per inode DAX flags.
Reviewed-by: Jan Kara
Signed-off-by: Ira Weiny
---
fs/ext4/ioctl.c | 4 ++--
1 file changed, 2 insertions(+), 2 del
From: Ira Weiny
Verity and DAX are incompatible. Changing the DAX mode due to a verity
flag change is wrong without a corresponding address_space_operations
update.
Make the 2 options mutually exclusive by returning an error if DAX was
set first.
(Setting DAX is already disabled if Verity is s
Use register_sysctl() to register the sysctl interface to avoid
merge conflicts when different features modify sysctl.c at the same time.
Here, the sysctl interfaces of hung task and watchdog are moved to the
corresponding feature code files
https://lkml.org/lkml/2020/5/11/1419
Xiaoming Ni (4):
Move watchdog sysctl interface to watchdog.c.
Use register_sysctl() to register the sysctl interface to avoid
merge conflicts when different features modify sysctl.c at the same time.
Signed-off-by: Xiaoming Ni
---
kernel/sysctl.c | 96
kernel/watc
1 - 100 of 1574 matches
Mail list logo
