Re: Subject: Re: [PATCH v3] kbuild: add support for zstd compressed modules

2021-04-09 Thread Sedat Dilek
On Fri, Apr 9, 2021 at 1:31 PM Sedat Dilek wrote: > > On Fri, Apr 9, 2021 at 1:10 PM Piotr Gorski wrote: > > > > I originally posted the patch in a different form [1] even before > > Masahiro's changes. > > I've been testing this solution since December last ye

Re: Subject: Re: [PATCH v3] kbuild: add support for zstd compressed modules

2021-04-09 Thread Sedat Dilek
On Fri, Apr 9, 2021 at 1:10 PM Piotr Gorski wrote: > > I originally posted the patch in a different form [1] even before Masahiro's > changes. > I've been testing this solution since December last year and posted it in > March this year, > after I made sure everything was working fine. This

Re: Subject: Re: [PATCH v3] kbuild: add support for zstd compressed modules

2021-04-09 Thread Sedat Dilek
On Thu, Apr 8, 2021 at 11:05 PM Piotr Gorski wrote: > > No, the --rm option is essential. xz and gzip have the --rm option built in > as opposed to zstd, which is why I used it. I've been using zstd module > compression since last december (although I set a different compression level > on

Re: Usage of CXX in tools directory

2021-04-04 Thread Sedat Dilek
> So you need to pass CXX=clang++ manually when playing in tools directory: > > MAKE="make V=1 > MAKE_OPTS="HOSTCC=clang HOSTCXX=clang++ HOSTLD=ld.lld CC=clang > CXX=clang++ LD=ld.lld LLVM=1 LLVM_IAS=1" > MAKE_OPTS="MAKE_OPTS $PAHOLE=/opt/pahole/bin/pahole" > > $ LC_ALL=C $MAKE $MAKE_OPTS -C

Usage of CXX in tools directory

2021-04-04 Thread Sedat Dilek
[ Please CC me I am not subscribed to all mailing-lists ] [ Please CC some more folks if you like ] Hi, when dealing/experimenting with BPF together with pahole/dwarves and dwarf-v5 and clang-lto I fell over that there is usage of CXX in tools directory. Especially, I wanted to build and run

Re: [PATCH] qemu_fw_cfg: Make fw_cfg_rev_attr a proper kobj_attribute

2021-04-02 Thread Sedat Dilek
On Fri, Apr 2, 2021 at 8:31 PM Nathan Chancellor wrote: > > On Fri, Apr 02, 2021 at 11:25:42AM -0700, Kees Cook wrote: > > On Fri, Apr 02, 2021 at 08:42:07AM +0200, Sedat Dilek wrote: > > > On Thu, Feb 25, 2021 at 10:25 PM Kees Cook wrote: > > > > > >

Re: [PATCH] qemu_fw_cfg: Make fw_cfg_rev_attr a proper kobj_attribute

2021-04-02 Thread Sedat Dilek
/cfi/cleanups, thanks! > > [1/1] qemu_fw_cfg: Make fw_cfg_rev_attr a proper kobj_attribute > https://git.kernel.org/kees/c/f5c4679d6c49 > I have queued this up in my custom patchset (for-5.12/kspp-cfi-cleanups-20210225). What is the plan to get this upstream? Feel free to add my: Tested-by: Sedat Dilek - Sedat -

Re: [PATCH 0/2] x86: Remove ideal_nops[]

2021-03-30 Thread Sedat Dilek
On Sat, Mar 27, 2021 at 9:02 PM Linus Torvalds wrote: > > On Sat, Mar 27, 2021 at 5:08 AM Sedat Dilek wrote: > > > > debian-5.10.19 as host-kernel: > > 11655.755564957 seconds time elapsed > > > > dileks-5.12-rc3 plus x86-nops as host-kernel: > > 11941

Re: [PATCH 0/3] Fix CONFIG_FUNCTION_TRACER with clang

2021-03-27 Thread Sedat Dilek
On Fri, Mar 26, 2021 at 2:07 PM Nathan Chancellor wrote: > > On Fri, Mar 26, 2021 at 09:37:55AM +0100, Sedat Dilek wrote: > > On Thu, Mar 25, 2021 at 11:38 PM Nathan Chancellor > > wrote: > > > > > > Hi all, > > > > > > This series fixes fu

Re: [PATCH 0/2] x86: Remove ideal_nops[]

2021-03-27 Thread Sedat Dilek
Out of curiosity I tried in my build-environment and my testing-rules to have comparable numbers... ..without passing "V=1" and "KBUILD_VERBOSE=1" as make-options: NOTE: Identical linux-config plus LLVM/Clang v12.0.0-rc3. debian-5.10.19 as host-kernel: 11655.755564957 seconds time elapsed

Re: linux-next: build failure after merge of the tip tree

2021-03-27 Thread Sedat Dilek
On Fri, Mar 26, 2021 at 2:11 PM Borislav Petkov wrote: > > On Fri, Mar 26, 2021 at 09:57:43AM +0100, Sedat Dilek wrote: > > The commit b90829704780 "bpf: Use NOP_ATOMIC5 instead of > > emit_nops(, 5) for BPF_TRAMP_F_CALL_ORIG" is now in Linus Git > > (see [1]).

Re: linux-next: build failure after merge of the tip tree

2021-03-26 Thread Sedat Dilek
On Mon, Mar 22, 2021 at 10:02 AM Borislav Petkov wrote: > > On Mon, Mar 22, 2021 at 02:37:14PM +1100, Stephen Rothwell wrote: > > Hi all, > > > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > > failed like this: > > > > arch/x86/net/bpf_jit_comp.c: In function

Re: [PATCH 1/3] x86: Propagate $(CLANG_FLAGS) to $(REALMODE_FLAGS)

2021-03-26 Thread Sedat Dilek
ated-as' tells clang to assemble with GNU Assembler > instead of its built-in LLVM assembler. This flag is set by default > unless `LLVM_IAS=1' is set, because the LLVM assembler can't yet > parse certain GNU extensions. > > Signed-off-by: John Millikin > Tested-by: Seda

Re: [PATCH 0/3] Fix CONFIG_FUNCTION_TRACER with clang

2021-03-26 Thread Sedat Dilek
On Thu, Mar 25, 2021 at 11:38 PM Nathan Chancellor wrote: > > Hi all, > > This series fixes function tracing with clang. > > Patch 1 adjusts the mcount regex in scripts/recordmcount.pl to handle > the presence of PLT relocations, which happen with clang. Without this, > the mcount_loc section

Re: [PATCH] iwlwifi: Fix softirq/hardirq disabling in iwl_pcie_enqueue_hcmd()

2021-03-23 Thread Sedat Dilek
On Mon, Mar 22, 2021 at 1:13 PM Jiri Kosina wrote: > > On Sat, 13 Mar 2021, Luca Coelho wrote: > > > > > > > > > > It's possible for iwl_pcie_enqueue_hcmd() to be called with > > > > > > > > > hard IRQs > > > > > > > > > disabled (e.g. from LED core). We can't enable BHs in such a > > > > > > >

Re: linux-next: build failure after merge of the tip tree

2021-03-23 Thread Sedat Dilek
On Mon, Mar 22, 2021 at 4:39 AM Stephen Rothwell wrote: > > Hi all, > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > arch/x86/net/bpf_jit_comp.c: In function 'arch_prepare_bpf_trampoline': > arch/x86/net/bpf_jit_comp.c:2015:16: error:

Re: [PATCH 0/2] x86: Remove ideal_nops[]

2021-03-15 Thread Sedat Dilek
On Mon, Mar 15, 2021 at 11:14 PM Peter Zijlstra wrote: > > On Mon, Mar 15, 2021 at 07:23:29PM +0100, Sedat Dilek wrote: > > > You mean something like that ^^? > > > > - Sedat - > > > > [1] > > https://git.zx2c4.com/laptop-kernel/commit/?id=116badbe

Re: [PATCH 0/2] x86: Remove ideal_nops[]

2021-03-15 Thread Sedat Dilek
On Mon, Mar 15, 2021 at 7:10 PM Peter Zijlstra wrote: > > On Mon, Mar 15, 2021 at 06:04:41PM +0100, Sedat Dilek wrote: > > > make V=1 -j4 LLVM=1 LLVM_IAS=1 > > So for giggles I checked, neither GCC nor LLVM seem to emit prefix NOPs > when building with -march=sandybrid

Re: [PATCH 0/2] x86: Remove ideal_nops[]

2021-03-15 Thread Sedat Dilek
On Mon, Mar 15, 2021 at 6:15 PM Borislav Petkov wrote: > > On Mon, Mar 15, 2021 at 06:04:41PM +0100, Sedat Dilek wrote: > > Here some fresh numbers: > > Lemme paste my previous reply which still holds true here: > > "There's a reason I have -s for silent in the bui

Re: [PATCH 0/2] x86: Remove ideal_nops[]

2021-03-15 Thread Sedat Dilek
On Sat, Mar 13, 2021 at 2:47 PM Sedat Dilek wrote: [ ... ] > Let me look if I will do a selfmade ThinLTO+PGO optimized LLVM > toolchain v12.0.0-rc3 this weekend. > I did it. Here some fresh numbers: [ Selfmade LLVM toolchain v12.0.0-rc3 "stage1-only" ] [ Host-Kernel: 5.12.0-

Re: [PATCH v2 1/2] Makefile: Remove '--gcc-toolchain' flag

2021-03-15 Thread Sedat Dilek
2: > > > > * Improve commit message (add history behind flag and link to Fangrui's > > documentation improvement). > > > Both applied to linux-kbuild. Thanks. > Sorry for being pedantic: This misses my Tested-by#s (see [1]). Tested-by: Sedat Dilek # LLVM/Clang v13-g

Re: [PATCH 0/2] x86: Remove ideal_nops[]

2021-03-13 Thread Sedat Dilek
On Sat, Mar 13, 2021 at 2:29 PM Borislav Petkov wrote: > > On Sat, Mar 13, 2021 at 01:58:56PM +0100, Sedat Dilek wrote: > > You can add Debian/experimental APT sources.list ... > > I could but I don't expect clang12 to behave any differently here. > Agreed in things of b

Re: [PATCH 0/2] x86: Remove ideal_nops[]

2021-03-13 Thread Sedat Dilek
On Sat, Mar 13, 2021 at 1:49 PM Borislav Petkov wrote: > > On Sat, Mar 13, 2021 at 01:38:22PM +0100, Sedat Dilek wrote: > > AFAICS you did a 5 times x86-64 defconfig with dropped pagecache and `make > > -j9`? > > The tailored .config for that particular test box. >

Re: [PATCH 0/2] x86: Remove ideal_nops[]

2021-03-13 Thread Sedat Dilek
On Sat, Mar 13, 2021 at 1:15 PM Borislav Petkov wrote: > > On Sat, Mar 13, 2021 at 01:10:29PM +0100, Sedat Dilek wrote: > > Here we go: > > > > https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/patch/?id=864b435514b286c0be2a38a02f487aa28d990ef8 > > That's

Re: [PATCH 0/2] x86: Remove ideal_nops[]

2021-03-13 Thread Sedat Dilek
On Sat, Mar 13, 2021 at 9:51 AM Borislav Petkov wrote: > > On Sat, Mar 13, 2021 at 06:26:15AM +0100, Sedat Dilek wrote: > > x86/jump_label: Mark arguments as const to satisfy asm constraints > > Where do I find this patch? > Here we go: https://git.kernel.org/pub/scm

Re: [PATCH] iwlwifi: Fix softirq/hardirq disabling in iwl_pcie_enqueue_hcmd()

2021-03-12 Thread Sedat Dilek
low. > >> > >> Hi, > >> > >> friendly ping on this one ... > > > > Luca, > > > > Johannes is telling me that he merged this patch internally, but I have no > > idea what is happening to it ... ? > > > > The reported splat is a

Re: [PATCH 0/2] x86: Remove ideal_nops[]

2021-03-12 Thread Sedat Dilek
On Fri, Mar 12, 2021 at 7:13 PM Sedat Dilek wrote: > > On Fri, Mar 12, 2021 at 6:47 PM Steven Rostedt wrote: > > > > On Fri, 12 Mar 2021 18:35:45 +0100 > > Sedat Dilek wrote: > > > > > > > Hey Steve, you degraded me to a number :-). &g

Re: [xhci] usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd

2021-03-12 Thread Sedat Dilek
On Fri, Mar 12, 2021 at 7:05 PM Alan Stern wrote: > > On Fri, Mar 12, 2021 at 06:41:58PM +0100, Sedat Dilek wrote: > > OK, now for the records: > > > > [ /etc/modprobe.d/usb-storage.conf ] > > > > # Add quirks for USB Mass Storage devices > > # > &

Re: [PATCH 0/2] x86: Remove ideal_nops[]

2021-03-12 Thread Sedat Dilek
On Fri, Mar 12, 2021 at 6:47 PM Steven Rostedt wrote: > > On Fri, 12 Mar 2021 18:35:45 +0100 > Sedat Dilek wrote: > > > > Hey Steve, you degraded me to a number :-). > > It's the internet, everyone is a number. > > > > > I dunno which Git tree this

Re: [xhci] usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd

2021-03-12 Thread Sedat Dilek
OK, now for the records: [ /etc/modprobe.d/usb-storage.conf ] # Add quirks for USB Mass Storage devices # # Link: https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html # # Option #1: Use Kernel command line parameter # [1] Usage: usb-storage.quirks= # [2] VendorID (VID) and

Re: [PATCH 0/2] x86: Remove ideal_nops[]

2021-03-12 Thread Sedat Dilek
On Fri, Mar 12, 2021 at 6:26 PM Steven Rostedt wrote: > > On Fri, 12 Mar 2021 15:47:26 +0100 > Borislav Petkov wrote: > > > On Fri, Mar 12, 2021 at 03:29:48PM +0100, Sedat Dilek wrote: > > > What does this change exactly mean to/for me? > > > > Probably not

Re: [xhci] usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd

2021-03-12 Thread Sedat Dilek
On Fri, Mar 12, 2021 at 5:57 PM Sedat Dilek wrote: > > On Sun, Mar 7, 2021 at 6:07 PM Alan Stern wrote: > > > > On Sun, Mar 07, 2021 at 05:57:39PM +0100, Sedat Dilek wrote: > > > On Sun, Mar 7, 2021 at 4:46 PM Alan Stern > > > wrote: > > > >

Re: [PATCH 0/2] x86: Remove ideal_nops[]

2021-03-12 Thread Sedat Dilek
On Fri, Mar 12, 2021 at 1:00 PM Peter Zijlstra wrote: > > Hi! > > A while ago Steve complained about x86 being weird for having different NOPs > [1] > > Having cursed the same thing before, I figured it was time to look at the NOP > situation. > > 32bit simply isn't a performance target anymore,

Re: [PATCH] kbuild: collect minimum tool versions into scripts/min-tool-version.sh

2021-03-12 Thread Sedat Dilek
2.23.0 > $ scripts/min-tool-version.sh foo > foo: unknown tool > > Signed-off-by: Masahiro Yamada > Reviewed-by: Nathan Chancellor The idea with creating gcc, llvm, binutils etc. files containing the minimum version-string sounds good to me. This version here tested on

Re: [PATCH] [RFC] arm64: enable HAVE_LD_DEAD_CODE_DATA_ELIMINATION

2021-03-10 Thread Sedat Dilek
On Wed, Mar 10, 2021 at 10:47 PM Nicolas Pitre wrote: ... > > With CONFIG_TRIM_UNUSED_KSYMS=y I see a 3x-loops of building .version > > and folowing steps - got no answer if this is intended. > > Yes it is intended. I explained it here: > > https://lkml.org/lkml/2021/3/9/1099 > Ah, cool. Thanks

Re: [PATCH] [RFC] arm64: enable HAVE_LD_DEAD_CODE_DATA_ELIMINATION

2021-03-10 Thread Sedat Dilek
On Wed, Mar 10, 2021 at 10:08 PM Arnd Bergmann wrote: > > On Wed, Mar 10, 2021 at 9:50 PM Masahiro Yamada wrote: > > On Mon, Mar 1, 2021 at 10:11 AM Nicholas Piggin wrote: > > > Excerpts from Arnd Bergmann's message of February 27, 2021 7:49 pm: > > > > > masahiro@oscar:~/ref/linux$ echo 'void

Re: [xhci] usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd

2021-03-07 Thread Sedat Dilek
On Sun, Mar 7, 2021 at 4:46 PM Alan Stern wrote: > > On Sat, Mar 06, 2021 at 09:49:00PM +0100, Sedat Dilek wrote: > > > For testing purposes, I stopped these systemd services: > > > > 1. systemctl stop smartmontools.service > > > > 2. systemctl stop udisk

Re: [xhci] usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd

2021-03-06 Thread Sedat Dilek
On Sat, Mar 6, 2021 at 9:56 PM Sedat Dilek wrote: > > On Sat, Mar 6, 2021 at 9:49 PM Sedat Dilek wrote: > > > > On Sat, Mar 6, 2021 at 9:38 PM Sedat Dilek wrote: > > > > > > On Sat, Mar 6, 2021 at 9:26 PM Sedat Dilek wrote: > > > > &

Re: [xhci] usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd

2021-03-06 Thread Sedat Dilek
On Sat, Mar 6, 2021 at 9:49 PM Sedat Dilek wrote: > > On Sat, Mar 6, 2021 at 9:38 PM Sedat Dilek wrote: > > > > On Sat, Mar 6, 2021 at 9:26 PM Sedat Dilek wrote: > > > > > > On Sat, Mar 6, 2021 at 5:58 PM Alan Stern > > > wrote: > > > >

Re: [xhci] usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd

2021-03-06 Thread Sedat Dilek
On Sat, Mar 6, 2021 at 9:38 PM Sedat Dilek wrote: > > On Sat, Mar 6, 2021 at 9:26 PM Sedat Dilek wrote: > > > > On Sat, Mar 6, 2021 at 5:58 PM Alan Stern wrote: > > > > > > On Sat, Mar 06, 2021 at 07:42:30AM +0100, Sedat Dilek wrote: > > > > No

Re: [xhci] usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd

2021-03-06 Thread Sedat Dilek
On Sat, Mar 6, 2021 at 9:26 PM Sedat Dilek wrote: > > On Sat, Mar 6, 2021 at 5:58 PM Alan Stern wrote: > > > > On Sat, Mar 06, 2021 at 07:42:30AM +0100, Sedat Dilek wrote: > > > No, with Debian-Kernel 5.10.19-1 there are no xhci-resets: > > > > Is the

Re: [PATCH 1/2] iwlwifi: fix DVM build regression in 5.12-rc

2021-03-06 Thread Sedat Dilek
On Sat, Mar 6, 2021 at 9:27 PM Hugh Dickins wrote: > > On Sat, 6 Mar 2021, Sedat Dilek wrote: > > On Sat, Mar 6, 2021 at 8:48 PM Hugh Dickins wrote: > > > > > > There is no iwl_so_trans_cfg if CONFIG_IWLDVM but not CONFIG_IWLMVM: > > > move the CONFIG_IWL

Re: [PATCH 2/2] iwlwifi: fix DVM boot regression in 5.12-rc

2021-03-06 Thread Sedat Dilek
On Sat, Mar 6, 2021 at 8:50 PM Hugh Dickins wrote: > > No time_point op has been provided for DVM: check for NULL before > calling, to fix the oops (blank screen booting non-modular kernel). > > Fixes: d01293154c0a ("iwlwifi: dbg: add op_mode callback for collecting debug > data.") >

Re: [PATCH 1/2] iwlwifi: fix DVM build regression in 5.12-rc

2021-03-06 Thread Sedat Dilek
On Sat, Mar 6, 2021 at 8:48 PM Hugh Dickins wrote: > > There is no iwl_so_trans_cfg if CONFIG_IWLDVM but not CONFIG_IWLMVM: > move the CONFIG_IWLMVM guard up before the problematic SnJ workaround > to fix the build breakage. > > Fixes: 930be4e76f26 ("iwlwifi: add support for SnJ with Jf devices")

Re: [xhci] usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd

2021-03-06 Thread Sedat Dilek
On Sat, Mar 6, 2021 at 5:58 PM Alan Stern wrote: > > On Sat, Mar 06, 2021 at 07:42:30AM +0100, Sedat Dilek wrote: > > No, with Debian-Kernel 5.10.19-1 there are no xhci-resets: > > Is the kernel the only thing that is different? The rest of the > operating system and e

Re: Linux 5.12-rc1

2021-03-05 Thread Sedat Dilek
On Mon, Mar 1, 2021 at 10:34 PM Linus Torvalds wrote: > > On Mon, Mar 1, 2021 at 12:35 AM Sedat Dilek wrote: > > > > I wondered why there was approx. for 6 days no commits and got an > > answer from an LWN posting "5.12 Merge window delayed". > >

Re: [xhci] usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd

2021-03-05 Thread Sedat Dilek
On Fri, Mar 5, 2021 at 8:54 PM Sedat Dilek wrote: > > On Fri, Mar 5, 2021 at 8:47 PM Alan Stern wrote: > > > > On Fri, Mar 05, 2021 at 08:41:40PM +0100, Sedat Dilek wrote: > > > On Fri, Mar 5, 2021 at 8:30 PM Alan Stern > > > wrote: > > > > >

Re: [xhci] usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd

2021-03-05 Thread Sedat Dilek
On Fri, Mar 5, 2021 at 8:47 PM Alan Stern wrote: > > On Fri, Mar 05, 2021 at 08:41:40PM +0100, Sedat Dilek wrote: > > On Fri, Mar 5, 2021 at 8:30 PM Alan Stern wrote: > > > > Okay, that indicates the ATA commands are being sent not by the kernel > > > but by so

Re: [xhci] usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd

2021-03-05 Thread Sedat Dilek
On Fri, Mar 5, 2021 at 8:30 PM Alan Stern wrote: > > On Fri, Mar 05, 2021 at 08:22:22PM +0100, Sedat Dilek wrote: > > The quirks match: > > > > [Fri Mar 5 20:06:56 2021] usb-storage 4-1:1.0: USB Mass Storage device > > detected > > [Fri Mar 5 20:06:56 202

Re: [xhci] usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd

2021-03-05 Thread Sedat Dilek
On Fri, Mar 5, 2021 at 8:25 PM Alan Stern wrote: > > On Fri, Mar 05, 2021 at 08:05:49PM +0100, Sedat Dilek wrote: > > On Fri, Mar 5, 2021 at 5:07 PM Alan Stern wrote: > > > > Don't worry about trying to decode the output. To me it looks like the > > > dr

Re: [xhci] usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd

2021-03-05 Thread Sedat Dilek
On Fri, Mar 5, 2021 at 8:05 PM Sedat Dilek wrote: > > On Fri, Mar 5, 2021 at 5:07 PM Alan Stern wrote: > > > > On Fri, Mar 05, 2021 at 01:09:16PM +0100, Sedat Dilek wrote: > > > On Mon, Mar 1, 2021 at 4:53 PM Alan Stern > > > wrote: > > > [ ... ]

Re: [xhci] usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd

2021-03-05 Thread Sedat Dilek
On Fri, Mar 5, 2021 at 5:07 PM Alan Stern wrote: > > On Fri, Mar 05, 2021 at 01:09:16PM +0100, Sedat Dilek wrote: > > On Mon, Mar 1, 2021 at 4:53 PM Alan Stern wrote: > > [ ... ] > > > You can use usbmon on bus 4 to record the USB traffic. It may indicate

Re: [PATCH v2] sched: Optimize __calc_delta.

2021-03-04 Thread Sedat Dilek
On Thu, Mar 4, 2021 at 7:24 PM Sedat Dilek wrote: > > On Thu, Mar 4, 2021 at 6:34 PM 'Nick Desaulniers' via Clang Built > Linux wrote: > > > > On Wed, Mar 3, 2021 at 2:48 PM Josh Don wrote: > > > > > > From: Clement Courbet > > > > >

Re: [PATCH v2] sched: Optimize __calc_delta.

2021-03-04 Thread Sedat Dilek
On Thu, Mar 4, 2021 at 6:34 PM 'Nick Desaulniers' via Clang Built Linux wrote: > > On Wed, Mar 3, 2021 at 2:48 PM Josh Don wrote: > > > > From: Clement Courbet > > > > A significant portion of __calc_delta time is spent in the loop > > shifting a u64 by 32 bits. Use `fls` instead of iterating.

Re: [PATCH v2] iwlwifi: don't call netif_napi_add() with rxq->lock held (was Re: Lockdep warning in iwl_pcie_rx_handle())

2021-03-03 Thread Sedat Dilek
On Wed, Mar 3, 2021 at 1:38 AM Kalle Valo wrote: > > "Coelho, Luciano" writes: > > > On Tue, 2021-03-02 at 11:34 +0100, Jiri Kosina wrote: > >> From: Jiri Kosina > >> > >> We can't call netif_napi_add() with rxq-lock held, as there is a potential > >> for deadlock as spotted by lockdep (see

Re: [PATCH 1/2] Makefile: Remove '--gcc-toolchain' flag

2021-03-03 Thread Sedat Dilek
On Wed, Mar 3, 2021 at 4:25 AM Sedat Dilek wrote: > > On Tue, Mar 2, 2021 at 10:07 PM Nathan Chancellor wrote: > > > > This is not necessary anymore now that we specify '--prefix=', which > > tells clang exactly where to find the GNU cross tools. This has been > &g

Re: [PATCH 1/2] Makefile: Remove '--gcc-toolchain' flag

2021-03-03 Thread Sedat Dilek
On Tue, Mar 2, 2021 at 10:07 PM Nathan Chancellor wrote: > > This is not necessary anymore now that we specify '--prefix=', which > tells clang exactly where to find the GNU cross tools. This has been > verified with self compiled LLVM 10.0.1 and LLVM 13.0.0 as well as a > distribution version of

Re: [xhci] usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd

2021-03-01 Thread Sedat Dilek
On Wed, Feb 24, 2021 at 6:25 PM Sedat Dilek wrote: > > On Wed, Feb 24, 2021 at 2:44 PM Sedat Dilek wrote: > > > > Hi Mathias, > > > > I am here on Linux-v5.11-10201-gc03c21ba6f4e. > > > > I see a lot xhci-resets in my dmesg-log: > > > > roo

Linux 5.12-rc1

2021-03-01 Thread Sedat Dilek
[ Please CC me I am not subscribed to LKML ] [ Original post see [0] ] Hi Linus, Thanks for Linux v5.12-rc1 and all involved people. [ Delayed merge-window ] I wondered why there was approx. for 6 days no commits and got an answer from an LWN posting "5.12 Merge window delayed". Unsure, if

Re: [PATCH v2] kbuild: fix UNUSED_KSYMS_WHITELIST for Clang LTO

2021-02-27 Thread Sedat Dilek
On Sat, Feb 27, 2021 at 8:08 AM Sedat Dilek wrote: > > On Sat, Feb 27, 2021 at 7:55 AM Masahiro Yamada wrote: > > > > On Fri, Feb 26, 2021 at 6:26 PM Sedat Dilek wrote: > > > > > > On Fri, Feb 26, 2021 at 7:26 AM Masahiro Yamada > > > wrote: >

Re: [PATCH v2] kbuild: fix UNUSED_KSYMS_WHITELIST for Clang LTO

2021-02-26 Thread Sedat Dilek
On Sat, Feb 27, 2021 at 7:55 AM Masahiro Yamada wrote: > > On Fri, Feb 26, 2021 at 6:26 PM Sedat Dilek wrote: > > > > On Fri, Feb 26, 2021 at 7:26 AM Masahiro Yamada > > wrote: > > > > > > Commit fbe078d397b4 ("kbuild: lto: add a default list of

Re: [PATCH] [RFC] arm64: enable HAVE_LD_DEAD_CODE_DATA_ELIMINATION

2021-02-26 Thread Sedat Dilek
On Fri, Feb 26, 2021 at 10:51 AM Arnd Bergmann wrote: > > On Fri, Feb 26, 2021 at 10:05 AM Sedat Dilek wrote: > > On Fri, Feb 26, 2021 at 9:14 AM Arnd Bergmann wrote: > > > > > > BTW, is CONFIG_LD_DEAD_CODE_DATA_ELIMINATION=y setable for x86 (64bit)? &

Re: [PATCH v2] kbuild: fix UNUSED_KSYMS_WHITELIST for Clang LTO

2021-02-26 Thread Sedat Dilek
On Fri, Feb 26, 2021 at 7:26 AM Masahiro Yamada wrote: > > Commit fbe078d397b4 ("kbuild: lto: add a default list of used symbols") > does not work as expected if the .config file has already specified > CONFIG_UNUSED_KSYMS_WHITELIST="my/own/white/list" before enabling > CONFIG_LTO_CLANG. > > So,

Re: [PATCH] [RFC] arm64: enable HAVE_LD_DEAD_CODE_DATA_ELIMINATION

2021-02-26 Thread Sedat Dilek
On Fri, Feb 26, 2021 at 9:14 AM Arnd Bergmann wrote: > > On Fri, Feb 26, 2021 at 1:36 AM Sedat Dilek wrote: > > > > On Thu, Feb 25, 2021 at 12:21 PM Arnd Bergmann wrote: > > > > > > From: Arnd Bergmann > > > > > > When looking at ke

Re: [PATCH] [RFC] arm64: enable HAVE_LD_DEAD_CODE_DATA_ELIMINATION

2021-02-25 Thread Sedat Dilek
On Thu, Feb 25, 2021 at 12:21 PM Arnd Bergmann wrote: > > From: Arnd Bergmann > > When looking at kernel size optimizations, I found that arm64 > does not currently support HAVE_LD_DEAD_CODE_DATA_ELIMINATION, > which enables the --gc-sections flag to the linker. > > I see that for a defconfig

Re: [PATCH v9 0/3] Kbuild: DWARF v5 support

2021-02-25 Thread Sedat Dilek
On Fri, Feb 5, 2021 at 9:22 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:

Re: [PATCH] perf tools: Move feature cleanup under tools/build

2021-02-25 Thread Sedat Dilek
there's existing OUTPUT directory before calling the clean. > > Cc: Sedat Dilek For my new friends from linux-bpf and linux-perf... I tested your patch on top of Linux v5.11-10201-gc03c21ba6f4e. git checkout c03c21ba6f4e -b for-5.12/perf-tools_feature_cleanup-jolsa git branch --show-current

Re: [PATCH] qemu_fw_cfg: Make fw_cfg_rev_attr a proper kobj_attribute

2021-02-24 Thread Sedat Dilek
Chancellor > > Looks good to me. Thank you for sending the patch! > > Reviewed-by: Sami Tolvanen > Environment: Linux v5.11-10201-gc03c21ba6f4e plus Clang-CFI as of 24-Feb-2021 on top built with LLVM v13-git. Tested-by: Sedat Dilek - Sedat -

Re: [PATCH] drm/amd/pm/swsmu: Avoid using structure_size uninitialized in smu_cmn_init_soft_gpu_metrics

2021-02-24 Thread Sedat Dilek
t; Fixes: de4b7cd8cb87 ("drm/amd/pm/swsmu: unify the init soft gpu metrics > function") > Link: https://github.com/ClangBuiltLinux/linux/issues/1304 > Signed-off-by: Nathan Chancellor I fell over this today with Linux v5.11-10201-gc03c21ba6f4e. Tested-by: Sedat Dilek # LLVM/Clang

Re: [xhci] usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd

2021-02-24 Thread Sedat Dilek
On Wed, Feb 24, 2021 at 2:44 PM Sedat Dilek wrote: > > Hi Mathias, > > I am here on Linux-v5.11-10201-gc03c21ba6f4e. > > I see a lot xhci-resets in my dmesg-log: > > root# LC_ALL=C dmesg -T | grep 'usb 4-1: reset SuperSpeed Gen 1 USB > device number 2 using xhci_hcd' |

Re: clang-12: i386: Unsupported relocation type: R_386_PLT32 (4)

2021-02-22 Thread Sedat Dilek
On Mon, Feb 22, 2021 at 5:30 PM Naresh Kamboju wrote: > > On Mon, 22 Feb 2021 at 21:44, Sedat Dilek wrote: > > > > On Mon, Feb 22, 2021 at 5:08 PM Naresh Kamboju > > wrote: > > > > > > While building i386 configs on stable-rc 5.10, stable-rc 5.11 bra

Re: clang-12: i386: Unsupported relocation type: R_386_PLT32 (4)

2021-02-22 Thread Sedat Dilek
On Mon, Feb 22, 2021 at 5:08 PM Naresh Kamboju wrote: > > While building i386 configs on stable-rc 5.10, stable-rc 5.11 branch > and mainline > with clang-12 these following warnings and errors were noticed. > Hi Naresh, Please see commit bb73d07148c405c293e576b40af37737faf23a6a ("x86/build:

Re: [PATCH v2 1/2] x86/stackprotector/32: Make the canary into a regular percpu variable

2021-02-16 Thread Sedat Dilek
This patch also makes load_gs_index() work on 32-bit kernels. On > > 64-bit kernels, it loads the GS selector and updates the user > > GSBASE accordingly. (This is unchanged.) On 32-bit kernels, > > it loads the GS selector and updates GSBASE, which is now > > always the user base.

Re: [PATCH v2 1/2] x86/stackprotector/32: Make the canary into a regular percpu variable

2021-02-16 Thread Sedat Dilek
On Tue, Feb 16, 2021 at 5:21 PM Sean Christopherson wrote: > > On Sat, Feb 13, 2021, Andy Lutomirski wrote: > > diff --git a/arch/x86/kvm/svm/svm.c b/arch/x86/kvm/svm/svm.c > > index f923e14e87df..ec39073b4897 100644 > > --- a/arch/x86/kvm/svm/svm.c > > +++ b/arch/x86/kvm/svm/svm.c > > @@

Re: Linux 5.8-rc6

2021-02-14 Thread Sedat Dilek
On Mon, Aug 10, 2020 at 5:30 PM Geert Uytterhoeven wrote: > > Hi Sedat, > > On Tue, Jul 21, 2020 at 10:19 AM Sedat Dilek wrote: > > You happen to know if I can configure in my ~/.gitconfig to pull > > linux-git stuff from two repositories - check first git.ke

Re: [PATCH v2 0/2] Clean up x86_32 stackprotector

2021-02-14 Thread Sedat Dilek
On Sat, Feb 13, 2021 at 8:19 PM Andy Lutomirski wrote: > > x86_32 stackprotector is a maintenance nightmare. Clean it up. This > disables stackprotector on x86_32 on GCC 8.1 and on all clang > versions. Some clang people are cc'd. > > Changes from v1: > - Changelog fixes. > - Comment fixes

Re: [PATCH v2 1/2] x86/stackprotector/32: Make the canary into a regular percpu variable

2021-02-13 Thread Sedat Dilek
or and updates GSBASE, which is now > always the user base. This means that the overall effect is > the same on 32-bit and 64-bit, which avoids some ifdeffery. > > Cc: Sedat Dilek > Cc: Nick Desaulniers > Signed-off-by: Andy Lutomirski > --- > arch/x86/Kconfig

Re: [PATCH v2 0/2] Clean up x86_32 stackprotector

2021-02-13 Thread Sedat Dilek
On Sat, Feb 13, 2021 at 8:19 PM Andy Lutomirski wrote: > > x86_32 stackprotector is a maintenance nightmare. Clean it up. This > disables stackprotector on x86_32 on GCC 8.1 and on all clang > versions. Some clang people are cc'd. > > Changes from v1: > - Changelog fixes. > - Comment fixes

Re: [PATCH] x86: entry: Remove _TIF_SINGLESTEP define leftover

2021-02-13 Thread Sedat Dilek
On Mon, Feb 8, 2021 at 11:01 PM Kyle Huey wrote: > > Looks good to me. > Any other comments on this patch v2? Thanks. - Sedat - > - Kyle > > On Mon, Feb 8, 2021 at 1:43 PM Sedat Dilek wrote: > > > > After commit 6342adcaa683 ("entry: Ensure trap after si

Re: [ANNOUNCE] exfatprogs-1.1.0 version released

2021-02-10 Thread Sedat Dilek
On Wed, Feb 10, 2021 at 8:24 AM Sedat Dilek wrote: > > On Wed, Feb 10, 2021 at 5:51 AM Namjae Jeon wrote: > > > > Hope Sven will do a new release for Debian. > > > ( Note that Debian/bullseye release plans "Milestone 2" this Friday, > > > Feb

Re: [ANNOUNCE] exfatprogs-1.1.0 version released

2021-02-09 Thread Sedat Dilek
On Wed, Feb 10, 2021 at 5:51 AM Namjae Jeon wrote: > > Hope Sven will do a new release for Debian. > > ( Note that Debian/bullseye release plans "Milestone 2" this Friday, > > February 12th (see [1] > "Key > > release dates" > "[2021-Feb-12] Soft Freeze"). Dunno which impact this > > might

Re: [ANNOUNCE] exfatprogs-1.1.0 version released

2021-02-09 Thread Sedat Dilek
On Wed, Feb 10, 2021 at 12:50 AM Namjae Jeon wrote: > > Hi folk, > > We have released exfatprogs 1.1.0 version. In this release, exfatlabel > has been added to print or re-write volume label and volume serial value. > Also, A new dump.exfat util has been added to display statistics from > a given

[PATCH v2] x86: entry: Remove _TIF_SINGLESTEP define leftover

2021-02-08 Thread Sedat Dilek
ll return") CC: Kyle Huey Signed-off-by: Sedat Dilek --- Changes v1->v2: - Add closing parenthesis to Fixes tag arch/x86/include/asm/thread_info.h | 1 - 1 file changed, 1 deletion(-) diff --git a/arch/x86/include/asm/thread_info.h b/arch/x86/include/asm/thread_info.h index 0d751d5da7

[PATCH] x86: entry: Remove _TIF_SINGLESTEP define leftover

2021-02-08 Thread Sedat Dilek
all return" CC: Kyle Huey Signed-off-by: Sedat Dilek --- arch/x86/include/asm/thread_info.h | 1 - 1 file changed, 1 deletion(-) diff --git a/arch/x86/include/asm/thread_info.h b/arch/x86/include/asm/thread_info.h index 0d751d5da702..8861967e0305 100644 --- a/arch/x86/include/asm/thread_i

Re: ANNOUNCE: pahole v1.20 (gcc11 DWARF5's default, lots of ELF sections, BTF)

2021-02-08 Thread Sedat Dilek
On Mon, Feb 8, 2021 at 1:32 PM Arnaldo Carvalho de Melo wrote: > > Em Mon, Feb 08, 2021 at 03:44:54AM +0100, Sedat Dilek escreveu: > > On Thu, Feb 4, 2021 at 11:07 PM Arnaldo Carvalho de Melo > > wrote: > > > > > > Hi, > > > > > >

Re: ANNOUNCE: pahole v1.20 (gcc11 DWARF5's default, lots of ELF sections, BTF)

2021-02-07 Thread Sedat Dilek
On Thu, Feb 4, 2021 at 11:07 PM Arnaldo Carvalho de Melo wrote: > > Hi, > > The v1.20 release of pahole and its friends is out, mostly > addressing problems related to gcc 11 defaulting to DWARF5 for -g, > available at the usual places: > > Main git repo: > >

Re: [Linux v5.11-rc7] x86: entry: Leftover of _TIF_SINGLESTEP define?

2021-02-07 Thread Sedat Dilek
On Mon, Feb 8, 2021 at 12:25 AM Kyle Huey wrote: > > On Sun, Feb 7, 2021 at 3:09 PM Sedat Dilek wrote: > > > > Hi, > > > > congrats to Linux v5.11-rc7. > > > > after commit 6342adcaa683 ("entry: Ensure trap after single-step on > > system call

Re: [Linux v5.11-rc7] x86: entry: Leftover of _TIF_SINGLESTEP define?

2021-02-07 Thread Sedat Dilek
On Mon, Feb 8, 2021 at 12:27 AM Bhaskar Chowdhury wrote: > > On 00:08 Mon 08 Feb 2021, Sedat Dilek wrote: > >Hi, > > > >congrats to Linux v5.11-rc7. > > > >after commit 6342adcaa683 ("entry: Ensure trap after single-step on > >system call return&q

[Linux v5.11-rc7] x86: entry: Leftover of _TIF_SINGLESTEP define?

2021-02-07 Thread Sedat Dilek
Hi, congrats to Linux v5.11-rc7. after commit 6342adcaa683 ("entry: Ensure trap after single-step on system call return"): $ git grep '\_TIF_SINGLESTEP' arch/x86/ arch/x86/include/asm/thread_info.h:#define _TIF_SINGLESTEP (1 << TIF_SINGLESTEP) Is this a leftover and can be removed (now)?

Re: ERROR: INT DW_ATE_unsigned_1 Error emitting BTF type

2021-02-06 Thread Sedat Dilek
On Sat, Feb 6, 2021 at 9:13 PM Yonghong Song wrote: > > > > On 2/6/21 11:44 AM, Sedat Dilek wrote: > > On Sat, Feb 6, 2021 at 8:33 PM Yonghong Song wrote: > >> > >> > >> > >> On 2/6/21 11:28 AM, Sedat Dilek wrote: > >>> On Sat, Fe

Re: ERROR: INT DW_ATE_unsigned_1 Error emitting BTF type

2021-02-06 Thread Sedat Dilek
On Sat, Feb 6, 2021 at 8:33 PM Yonghong Song wrote: > > > > On 2/6/21 11:28 AM, Sedat Dilek wrote: > > On Sat, Feb 6, 2021 at 8:22 PM Sedat Dilek wrote: > >> > >> On Sat, Feb 6, 2021 at 8:17 PM Yonghong Song wrote: > >>> > >>> >

Re: ERROR: INT DW_ATE_unsigned_1 Error emitting BTF type

2021-02-06 Thread Sedat Dilek
On Sat, Feb 6, 2021 at 8:22 PM Sedat Dilek wrote: > > On Sat, Feb 6, 2021 at 8:17 PM Yonghong Song wrote: > > > > > > > > On 2/6/21 10:10 AM, Sedat Dilek wrote: > > > On Sat, Feb 6, 2021 at 6:53 PM Yonghong Song wrote: > > >> > >

Re: ERROR: INT DW_ATE_unsigned_1 Error emitting BTF type

2021-02-06 Thread Sedat Dilek
On Sat, Feb 6, 2021 at 8:17 PM Yonghong Song wrote: > > > > On 2/6/21 10:10 AM, Sedat Dilek wrote: > > On Sat, Feb 6, 2021 at 6:53 PM Yonghong Song wrote: > >> > >> > >> > >> On 2/6/21 8:24 AM, Mark Wieelard wrote: > >>> Hi, &

Re: ERROR: INT DW_ATE_unsigned_1 Error emitting BTF type

2021-02-06 Thread Sedat Dilek
On Sat, Feb 6, 2021 at 6:53 PM Yonghong Song wrote: > > > > On 2/6/21 8:24 AM, Mark Wieelard wrote: > > Hi, > > > > On Sat, Feb 06, 2021 at 12:26:44AM -0800, Yonghong Song wrote: > >> With the above vmlinux, the issue appears to be handling > >> DW_ATE_signed_1, DW_ATE_unsigned_{1,24,40}. > >> >

Re: ERROR: INT DW_ATE_unsigned_1 Error emitting BTF type

2021-02-06 Thread Sedat Dilek
Some post-mortem: LLVM_DWARF_BIN="/opt/llvm-toolchain/bin/llvm-dwarfdump" module="drivers/net/ethernet/mellanox/mlx5/core/mlx5_core.ko" Module has DW_ATE_unsigned_160 and DW_ATE_unsigned_1: $LLVM_DWARF_BIN $module | grep DW_AT_name | grep DW_ATE_ | sort -u DW_AT_name

Re: [PATCH v9 0/3] Kbuild: DWARF v5 support

2021-02-06 Thread Sedat Dilek
On Sat, Feb 6, 2021 at 1:05 PM Masahiro Yamada wrote: > > On Sat, Feb 6, 2021 at 6:00 AM Sedat Dilek wrote: > > > > On Fri, Feb 5, 2021 at 9:22 PM Nick Desaulniers > > wrote: > > > > > > DWARF v5 is the latest standard of the DWARF debug info for

Re: ERROR: INT DW_ATE_unsigned_1 Error emitting BTF type

2021-02-06 Thread Sedat Dilek
[ SNIP ] > > > > > Please help do a test. I can submit a formal patch tomorrow. > > > > > > > > Thanks for the patch. > > > > > > > > Can you attach the diff as Gmail has totally truncated/malformed it? > > > > > > > > For the Linux breakage - you will need some additional Clang specific > > > >

Re: ERROR: INT DW_ATE_unsigned_1 Error emitting BTF type

2021-02-06 Thread Sedat Dilek
On Sat, Feb 6, 2021 at 10:48 AM Sedat Dilek wrote: > > On Sat, Feb 6, 2021 at 10:32 AM Sedat Dilek wrote: > > > > On Sat, Feb 6, 2021 at 9:32 AM Sedat Dilek wrote: > > > > > > On Sat, Feb 6, 2021 at 9:27 AM Yonghong Song wrote: > > > > > &g

Re: ERROR: INT DW_ATE_unsigned_1 Error emitting BTF type

2021-02-06 Thread Sedat Dilek
On Sat, Feb 6, 2021 at 10:32 AM Sedat Dilek wrote: > > On Sat, Feb 6, 2021 at 9:32 AM Sedat Dilek wrote: > > > > On Sat, Feb 6, 2021 at 9:27 AM Yonghong Song wrote: > > > > > > > > > > > > On 2/5/21 10:52 PM, Sedat Dilek wrote: > > &g

Re: ERROR: INT DW_ATE_unsigned_1 Error emitting BTF type

2021-02-06 Thread Sedat Dilek
On Sat, Feb 6, 2021 at 10:32 AM Sedat Dilek wrote: > > On Sat, Feb 6, 2021 at 9:32 AM Sedat Dilek wrote: > > > > On Sat, Feb 6, 2021 at 9:27 AM Yonghong Song wrote: > > > > > > > > > > > > On 2/5/21 10:52 PM, Sedat Dilek wrote: > > &g

  1   2   3   4   5   6   7   8   9   10   >