Crazy robot, stop spamming. This report is obviously bogus, yet, you
sent me 5 copies.
Whoever is responsible for this, please sign emails with your real
name!
Pavel
On Sat 2020-12-19 14:19:16, kernel test robot wrote:
> tree:
syzbot has found a reproducer for the following issue on:
HEAD commit:a409ed15 Merge tag 'gpio-v5.11-1' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=174778a750
kernel config:
In case of error, we should call 'clk_disable_unprepare()' to undo a
previous 'clk_prepare_enable()' call, as already done in the remove
function.
Fixes: 406346d22278 ("hwrng: ingenic - Add hardware TRNG for Ingenic X1830")
Signed-off-by: Christophe JAILLET
---
On Sat, Dec 19, 2020 at 12:30:39PM +0900, Daejun Park wrote:
> @@ -323,6 +325,8 @@ static struct attribute *ufs_sysfs_device_descriptor[] = {
> _attr_number_of_secure_wpa.attr,
> _attr_psa_max_data_size.attr,
> _attr_psa_state_timeout.attr,
> + _attr_hpb_version.attr,
> +
On Sat, Dec 19, 2020 at 11:27:31AM +0800, zhangqiumi...@huwei.com wrote:
> From: zhangqiumiao
>
> Fix the problem that tty buffer data was not flushed when timeout=0.
>
> Signed-off-by: zhangqiumiao
> ---
> drivers/tty/tty_ioctl.c | 12 ++--
> 1 file changed, 10 insertions(+), 2
On 2020/12/19 10:41, Dan Williams wrote:
> There are multiple locations that open-code the release of the last
> range in a device-dax instance. Consolidate this into a new
> dev_dax_trim_range() helper.
>
> This also addresses a kmemleak report:
>
> # cat /sys/kernel/debug/kmemleak
> [..]
>
On Sat, Dec 19, 2020 at 8:53 AM Ian Kent wrote:
>
> On Fri, 2020-12-18 at 21:20 +0800, Fox Chen wrote:
> > On Fri, Dec 18, 2020 at 7:21 PM Ian Kent wrote:
> > > On Fri, 2020-12-18 at 16:01 +0800, Fox Chen wrote:
> > > > On Fri, Dec 18, 2020 at 3:36 PM Ian Kent
> > > > wrote:
> > > > > On Thu,
Linus,
The following changes since commit b3298500b23f0b53a8d81e0d5ad98a29db71f4f0:
Merge tag 'for-5.10/dm-fixes' of
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm
(2020-12-04 13:28:39 -0800)
are available in the Git repository at:
On Sat, Dec 19, 2020 at 02:26:09PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Commit
>
> 06148d3b3f2e ("xfrm: Fix oops in xfrm_replay_advance_bmp")
>
> is missing a Signed-off-by from its committer.
My bad. I did a forced push to fix it.
On Fri, 2020-12-18 at 09:59 -0500, Tejun Heo wrote:
> Hello,
>
> On Fri, Dec 18, 2020 at 03:36:21PM +0800, Ian Kent wrote:
> > Sounds like your saying it would be ok to add a lock to the
> > attrs structure, am I correct?
>
> Yeah, adding a lock to attrs is a lot less of a problem and it looks
>
Hello Linus,
Here the I3C PR for 5.11. This should be my last PR (I resigned from
my maintainer position). Alexandre Belloni (maintainer of the RTC
subsystem) kindly proposed to take over, so he should send the I3C PRs
from now on.
Regards,
Boris
The following changes since commit
On Thu, Nov 19, 2020 at 10:37:07AM -0800, Sean Christopherson wrote:
> From: Sean Christopherson
>
> Update my email address to one provided by my new benefactor.
>
> Cc: Thomas Gleixner
> Cc: Borislav Petkov
> Cc: Jarkko Sakkinen
> Cc: Dave Hansen
> Cc: Andy Lutomirski
> Cc: Vitaly
When using LLVM's integrated assembler (LLVM_IAS=1) while building
x86_64_defconfig + CONFIG_KVM=y + CONFIG_KVM_AMD=y, the following build
error occurs:
$ make LLVM=1 LLVM_IAS=1 arch/x86/kvm/svm/sev.o
arch/x86/kvm/svm/sev.c:2004:15: error: too few operands for instruction
asm
Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
for-linus-5.11-rc1b-tag
xen: branch for v5.11-rc1
It contains some minor cleanup patches and a small series disentangling some Xen
related Kconfig options.
Thanks.
Juergen
On 16.12.20 15:08, Jason Andryuk wrote:
commit bfda93aee0ec ("xen: Kconfig: nest Xen guest options")
accidentally re-added X86_64 as a dependency to XEN_512GB. It was
originally removed in commit a13f2ef168cb ("x86/xen: remove 32-bit Xen
PV guest support"). Remove it again.
Fixes:
-20201217
x86_64 randconfig-a016-20201218
x86_64 randconfig-a013-20201218
x86_64 randconfig-a012-20201218
x86_64 randconfig-a015-20201218
x86_64 randconfig-a014-20201218
x86_64 randconfig-a011-20201218
i386
Introducing a feature of CPU PARK in order to save time
of cpus down and up during kexec, which may cost 250ms of
per cpu's down and 30ms of up.
As a result, for 128 cores, it costs more than 30 seconds
to down and up cpus during kexec. Think about 256 cores and more.
CPU PARK is a state that
On 12/17/20 10:52 AM, Pavel Tatashin wrote:
>
Hi Pavel,
This all looks good pretty good to me, with just a couple of minor
doubts interleaved with the documentation tweaks:
a) I'm not yet sure if the is_pinnable_page() concept is a keeper. If it's
not for some reason, then we should revisit
Give the user a clue about the problem along with the 35 lines of
usage/help text.
Signed-off-by: Randy Dunlap
Cc: Andi Kleen
Cc: Masahiro Yamada
Cc: linux-kbu...@vger.kernel.org
---
scripts/config |1 +
1 file changed, 1 insertion(+)
--- linux-next-20201218.orig/scripts/config
+++ linux
tcc_syms.c| 17 -
3 files changed, 8 insertions(+), 18 deletions(-)
--- linux-next-20201218.orig/lib/zlib_dfltcc/dfltcc.c
+++ linux-next-20201218/lib/zlib_dfltcc/dfltcc.c
@@ -1,7 +1,8 @@
// SPDX-License-Identifier: Zlib
/* dfltcc.c - SystemZ DEFLATE CONVERSION CALL support. */
On Thu, 2020-12-17 at 20:17 +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> When turbo has been disabled by the BIOS, but HWP_CAP.GUARANTEED is
> changed later, user space may want to take advantage of this
> increased
> guaranteed performance.
>
> HWP_CAP.GUARANTEED is not a
On Wed, Nov 11, 2020 at 1:22 AM Serge Semin
wrote:
>
> In accordance with the DWC USB3 bindings the corresponding node
> name is suppose to comply with the Generic USB HCD DT schema, which
> requires the USB nodes to have the name acceptable by the regexp:
> "^usb(@.*)?" . Make sure the
A release candidate Git v2.30.0-rc1 is now available for testing
at the usual places. It is comprised of 455 non-merge commits
since v2.29.0, contributed by 72 people, 26 of which are new faces.
The tarballs are found at:
https://www.kernel.org/pub/software/scm/git/testing/
The following
From: Nadav Amit
Userfaultfd self-tests fail occasionally, indicating a memory
corruption.
Analyzing this problem indicates that there is a real bug since
mmap_lock is only taken for read in mwriteprotect_range(). This might
cause the TLBs to be in an inconsistent state due to the deferred
Hi,
On Fri, 2020-12-18 at 16:42 -0600, Rob Herring wrote:
> On Thu, Dec 17, 2020 at 7:48 PM Liu Ying wrote:
> >
> > Hi,
> >
> > On Thu, 2020-12-17 at 12:50 -0600, Rob Herring wrote:
> > > On Thu, 17 Dec 2020 17:59:23 +0800, Liu Ying wrote:
> > > > This patch adds bindings for i.MX8qm/qxp pixel
randconfig-a005-20201217
x86_64 randconfig-a016-20201218
x86_64 randconfig-a013-20201218
x86_64 randconfig-a012-20201218
x86_64 randconfig-a015-20201218
x86_64 randconfig-a014-20201218
x86_64 randconfig-a011-20201218
i386
On 12/17/20 9:37 AM, Md Sadre Alam wrote:
This change will add support for LOCK & UNLOCK flag bit support
on CMD descriptor.
If DMA_PREP_LOCK flag passed in prep_slave_sg then requester of this
transaction wanted to lock the DMA controller for this transaction so
BAM driver should set LOCK
This patch changes the read I/O to the HPB read I/O.
If the logical address of the read I/O belongs to active sub-region, the
HPB driver modifies the read I/O command to HPB read. It modifies the UPIU
command of UFS instead of modifying the existing SCSI command.
In the HPB version 1.0, the
If the available data to transfer is exactly a multiple of block size, save
the last block to be transferred in qce_ahash_final (with the last block
bit set) if this is indeed the end of data stream. If not this saved block
will be transferred as part of next update. If this block is not held back
This is a patch for managing L2P map in HPB module.
The HPB divides logical addresses into several regions. A region consists
of several sub-regions. The sub-region is a basic unit where L2P mapping is
managed. The driver loads L2P mapping data of each sub-region. The loaded
sub-region is called
src_table is unused and hence remove it from struct qce_cipher_reqctx
Signed-off-by: Thara Gopinath
---
drivers/crypto/qce/cipher.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/crypto/qce/cipher.h b/drivers/crypto/qce/cipher.h
index cffa9fc628ff..850f257d00f3 100644
---
Set the register REG_ENCR_XTS_DU_SIZE to cryptlen for AES XTS
transformation. Anything else causes the engine to return back
wrong results.
Signed-off-by: Thara Gopinath
---
drivers/crypto/qce/common.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
This patch contains the following fixes for the supported encryption
algorithms in the Qualcomm crypto engine(CE)
1. Return unsupported if key1 = key2 for AES XTS algorithm since CE
does not support this and the operation causes the engine to hang.
2. Return unsupprted if any three keys are same
totallen is used to get the size of the data to be transformed.
This is also available via nbytes or cryptlen in the qce_sha_reqctx
and qce_cipher_ctx. Similarly offset convey nothing for the supported
encryption and authentication transformations and is always 0.
Remove these two redundant
This is a patch for the HPB initialization and adds HPB function calls to
UFS core driver.
NAND flash-based storage devices, including UFS, have mechanisms to
translate logical addresses of IO requests to the corresponding physical
addresses of the flash storage.
In UFS,
Export and import interfaces save and restore partial transformation
states. The partial states were being stored and restored in struct
sha1_state for sha1/hmac(sha1) transformations and sha256_state for
sha256/hmac(sha256) transformations.This led to a bunch of corner cases
where improper state
Changelog:
v14 -> v15
1. Remove duplicated sysfs ABI entries in documentation.
2. Add experiment result of HPB performance testing with iozone.
v13 -> v14
1. Cleanup codes by commentted in Greg's review.
2. Add documentation for sysfs entries (from Greg's review).
3. Add experiment result of HPB
This patch series is a result of running kernel crypto fuzz tests (by
enabling CONFIG_CRYPTO_MANAGER_EXTRA_TESTS) on the transformations
currently supported via the Qualcomm crypto engine on sdm845.
The first four patches are fixes for various regressions found during
testing. The last two patches
Hi all,
Commit
06148d3b3f2e ("xfrm: Fix oops in xfrm_replay_advance_bmp")
is missing a Signed-off-by from its committer.
--
Cheers,
Stephen Rothwell
pgpELN38Ev1kg.pgp
Description: OpenPGP digital signature
On 12/19/20 9:21 AM, Chris Down wrote:
Jacob Wen writes:
set_task_reclaim_state() is a function with 3 lines of code of which
2 lines contain WARN_ON_ONCE.
I am not comfortable with the current repetition.
Ok, but could you please go into _why_ others should feel that way
too? There are
syzbot suspects this issue was fixed by commit:
commit e722a295cf493388dae474745d30e91e1a2ec549
Author: Greg Kroah-Hartman
Date: Thu Aug 27 12:36:27 2020 +
staging: ion: remove from the tree
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17d4f13750
start commit:
There are multiple locations that open-code the release of the last
range in a device-dax instance. Consolidate this into a new
dev_dax_trim_range() helper.
This also addresses a kmemleak report:
# cat /sys/kernel/debug/kmemleak
[..]
unreferenced object 0x976bd46f6240 (size 64):
comm
From: Xuewen Yan
CPU (root cfs_rq) estimated utilization (util_est) is currently used in
dequeue_task_fair() to drive frequency selection before it is updated.
with:
CPU_util: rq->cfs.avg.util_avg
CPU_util_est: rq->cfs.avg.util_est
CPU_utilization : max(CPU_util, CPU_util_est)
On Fri, Dec 18, 2020 at 06:01:01PM +0100, Ard Biesheuvel wrote:
>
> Questions:
> - what did I miss or break horribly?
> - does any of this matter for RT? AIUI, RT runs softirqs from a dedicated
> kthread, so I don't think it cares.
> - what would be a reasonable upper bound to keep softirqs
This patch fixes the checkpatch warning:
WARNING: Possible repeated word: 'and'
Signed-off-by: Daniel West
---
drivers/staging/qlge/qlge_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/qlge/qlge_main.c b/drivers/staging/qlge/qlge_main.c
index
pcf2127, pcf2129 and pca2129 support start-year and reset-source.
Signed-off-by: Alexandre Belloni
---
.../devicetree/bindings/rtc/nxp,pcf2127.yaml | 54 +++
.../devicetree/bindings/rtc/trivial-rtc.yaml | 6 ---
2 files changed, 54 insertions(+), 6 deletions(-)
create mode
On 12/18/20 4:11 AM, Uros Bizjak wrote:
Merge __kvm_handle_fault_on_reboot with its sole user
and move the definition of __ex to a common include to be
shared between VMX and SVM.
Cc: Paolo Bonzini
Cc: Sean Christopherson
Signed-off-by: Uros Bizjak
---
arch/x86/include/asm/kvm_host.h |
Jacob Wen writes:
set_task_reclaim_state() is a function with 3 lines of code of which 2
lines contain WARN_ON_ONCE.
I am not comfortable with the current repetition.
Ok, but could you please go into _why_ others should feel that way too? There
are equally also reasons to err on the side of
On Fri, Dec 18, 2020 at 6:36 AM Daniel Vetter wrote:
> On Thu, Dec 17, 2020 at 11:06:11PM +, John Stultz wrote:
> > Reuse/abuse the pagepool code from the network code to speed
> > up allocation performance.
> >
> > This is similar to the ION pagepool usage, but tries to
> > utilize generic
On Sat, Dec 19, 2020 at 1:59 AM Valentin Schneider
wrote:
>
>
> On 18/12/20 17:09, Lai Jiangshan wrote:
> > From: Lai Jiangshan
> >
> > When worker_attach_to_pool() is called, we should not put the workers
> > to pool->attrs->cpumask when there is not CPU online in it.
> >
> > We have to use
On Wed, Dec 16, 2020 at 5:16 PM Paul E. McKenney wrote:
> In my experience, lockdep will indeed complain if an interrupt handler
> returns while in an RCU read-side critical section.
Can't we add lock status checks into the beginning and the end of interrupt
handler functions
(e.g. whether
On Fri, 18 Dec 2020 11:10:52 +0100, Rasmus Villemoes wrote:
> This adds a reset-source RTC DT binding, as suggested by Alexandre,
> and resends Uwe's patch making use of that property in pcf2127 driver
> to avoid the driver exposing a watchdog that doesn't work (and
> potentially shuffling the
On Fri, Dec 18, 2020 at 12:35:09PM -0800, Linus Torvalds wrote:
> On Fri, Dec 18, 2020 at 8:04 AM Thierry Reding
> wrote:
> >
> > This is a fairly big release cycle from the PWM framework's point of
> > view.
>
> Why does all of this have commit dates from the last day?
>
> It clearly cannot
On Fri, 2020-12-18 at 21:20 +0800, Fox Chen wrote:
> On Fri, Dec 18, 2020 at 7:21 PM Ian Kent wrote:
> > On Fri, 2020-12-18 at 16:01 +0800, Fox Chen wrote:
> > > On Fri, Dec 18, 2020 at 3:36 PM Ian Kent
> > > wrote:
> > > > On Thu, 2020-12-17 at 10:14 -0500, Tejun Heo wrote:
> > > > > Hello,
> >
On Fri, Dec 18, 2020 at 04:15:45PM -0600, Rob Herring wrote:
> On Thu, Dec 17, 2020 at 9:00 AM Thierry Reding
> wrote:
> >
> > On Tue, Nov 10, 2020 at 08:33:09PM +0100, Thierry Reding wrote:
> > > On Fri, Nov 06, 2020 at 04:25:48PM +0100, Thierry Reding wrote:
> > > > On Thu, Nov 05, 2020 at
Hi Daniel,
On Fri, Dec 18, 2020 at 11:57:54PM +, Daniel Scally wrote:
> Hi Laurent - thanks for the comments
>
> On 18/12/2020 16:53, Laurent Pinchart wrote:
> >> +static void cio2_bridge_init_property_names(struct cio2_sensor *sensor)
> >> +{
> >> +
The mm-of-the-moment snapshot 2020-12-18-16-27 has been uploaded to
https://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
https://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You
Hi Andy, thanks for the comments
On 18/12/2020 21:17, Andy Shevchenko wrote:
> On Thu, Dec 17, 2020 at 11:43:37PM +, Daniel Scally wrote:
>> Currently on platforms designed for Windows, connections between CIO2 and
>> sensors are not properly defined in DSDT. This patch extends the ipu3-cio2
On 18/12/2020 19:36:08-0400, Jason Gunthorpe wrote:
> On Fri, Dec 18, 2020 at 10:16:58PM +0100, Alexandre Belloni wrote:
>
> > But then again, what about non-enumerable devices on the PCI device? I
> > feel this would exactly fit MFD. This is a collection of IPs that exist
> > as standalone but
We should call irq trace only if interrupt is going to be enabled during
excecption handling. Otherwise, it results in following warning during
boot with lock debugging enabled.
[0.00] [ cut here ]
[0.00] DEBUG_LOCKS_WARN_ON(early_boot_irqs_disabled)
[
Jarod Wilson wrote:
>This comes from an end-user request, where they're running multiple VMs on
>hosts with bonded interfaces connected to some interest switch topologies,
>where 802.3ad isn't an option. They're currently running a proprietary
>solution that effectively achieves load-balancing
memblock_enforce_memory_limit accepts the maximum memory size not the
maximum address that can be handled by kernel. Fix the function invocation
accordingly.
Fixes: 1bd14a66ee52 ("RISC-V: Remove any memblock representing unusable memory
area")
Cc: sta...@vger.kernel.org
Reported-by: Bin Meng
On Fri, Dec 18, 2020 at 02:59:00PM -0800, Randy Dunlap wrote:
> On 12/1/20 2:34 PM, mgr...@linux.intel.com wrote:
> > From: Srikanth Thokala
> >
> > Provide overview of XLink PCIe driver implementation
> >
> > Cc: linux-...@vger.kernel.org
> > Reviewed-by: Mark Gross
> > Signed-off-by:
The pid_revalidate() function requires dropping from RCU into REF lookup
mode. When many threads are resolving paths within /proc in parallel,
this can result in heavy spinlock contention on d_locrkef as each thread
tries to grab a reference to the /proc dentry (and drop it shortly
thereafter).
Smack needs its security_task_to_inode() hook to be called when a task
execs a new executable. Store the self_exec_id of the task and call the
hook via pid_update_inode() whenever the exec_id changes.
Signed-off-by: Stephen Brennan
---
As discussed on the v2 of the patch, this should allow
Hi Linus,
The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec:
Linux 5.10-rc1 (2020-10-25 15:14:11 -0700)
are available in the Git repository at:
ssh://g...@gitolite.kernel.org/pub/scm/linux/kernel/git/sre/linux-power-supply.git
tags/for-v5.11
for you to fetch
Hi Linus,
The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec:
Linux 5.10-rc1 (2020-10-25 15:14:11 -0700)
are available in the Git repository at:
ssh://g...@gitolite.kernel.org/pub/scm/linux/kernel/git/sre/linux-hsi.git
tags/hsi-for-5.11
for you to fetch changes
Hi Laurent - thanks for the comments
On 18/12/2020 16:53, Laurent Pinchart wrote:
>> +static void cio2_bridge_init_property_names(struct cio2_sensor *sensor)
>> +{
>> +strscpy(sensor->prop_names.clock_frequency, "clock-frequency",
>> +sizeof(sensor->prop_names.clock_frequency));
On Tue, Dec 8, 2020 at 3:35 PM Jay Vosburgh wrote:
>
> Jarod Wilson wrote:
...
> >The addition of a case BOND_LINK_BACK in bond_miimon_commit() is somewhat
> >separate from the fix for the actual hang, but it eliminates a constant
> >"invalid new link 3 on slave" message seen related to this
On 18/12/2020 22:13, Daniel Scally wrote:
>>> + break;
>>> + }
>>> +
>>> + /* No more endpoints for that port, so stop passing old */
>>> + old = NULL;
>>
>> I wonder if you could drop the 'old' variable and use 'enpoint' in the
>> call to
On Fri, Dec 18, 2020 at 10:16:58PM +0100, Alexandre Belloni wrote:
> But then again, what about non-enumerable devices on the PCI device? I
> feel this would exactly fit MFD. This is a collection of IPs that exist
> as standalone but in this case are grouped in a single device.
So, if mfd had a
Hi--
On 12/1/20 2:34 PM, mgr...@linux.intel.com wrote:
> From: mark gross
>
>
> Reviewed-by: Mark Gross
> Signed-off-by: Mark Gross
My reading of submitting-patches.rst seems to indicate that
the Reviewer and Submitter are probably not the same person.
Are you sure that you reviewed it?
Hi, Dmitry,
Thanks for you suggestion. I have sent v3 version of the patch where I
have applied it.
Kind regards,
Vasyl
On 09.12.20 00:05, Dmitry Torokhov wrote:
CAUTION: This email originated from outside of the organization.
Do not click links or open attachments unless you recognize the
From: Mathias Crombez
Without multi-touch slots allocated, ABS_MT_SLOT events will be lost by
input_handle_abs_event.
Implementation is based on uinput_create_device.
Signed-off-by: Mathias Crombez
Co-developed-by: Vasyl Vavrychuk
Signed-off-by: Vasyl Vavrychuk
---
v2: fix patch corrupted
From: Mathias Crombez
Without multi-touch slots allocated, ABS_MT_SLOT events will be lost by
input_handle_abs_event.
Implementation is based on uinput_create_device.
Signed-off-by: Mathias Crombez
Co-developed-by: Vasyl Vavrychuk
Signed-off-by: Vasyl Vavrychuk
---
v2: fix patch corrupted
On 09.12.20 10:28, Michael S. Tsirkin wrote:
On Tue, Dec 08, 2020 at 11:01:50PM +0200, Vasyl Vavrychuk wrote:
From: Mathias Crombez
Cc: sta...@vger.kernel.org
I don't believe this is appropriate for stable, looks like
a new feature to me.
Agree, removed.
+config
Hi Geert,
On 18/12/20 13:52, Geert Uytterhoeven wrote:
> Commit 45c940184b501fc6 ("dt-bindings: clk: versaclock5: convert to
> yaml") accidentally changed "idt,voltage-microvolts" to
> "idt,voltage-microvolt" in the DT bindings, while the driver still used
> the former.
>
> Update the driver to
Define per-queue locks for protecting queue state and event pool
sent/free lists. The evt list lock is initially redundant but it allows
the driver to be modified in the follow-up patches to relax the queue
locking around submissions and completions.
Signed-off-by: Tyrel Datwyler
Reviewed-by:
The primary and async CRQs are nearly identical outside of the format
and length of each message entry in the dma mapped page that represents
the queue data. These queues can be represented with a generic queue
structure that uses a union to differentiate between message format of
the mapped page.
There is currently a single command event pool per host. In anticipation
of providing multiple queues add a per-queue event pool definition and
reimplement the existing CRQ to use its queue defined event pool for
command submission and completion.
Signed-off-by: Tyrel Datwyler
Reviewed-by: Brian
Drain the command queue and place all commands on a completion list.
Perform command completion on that list outside the host/queue locks.
Further, move purged command compeletions outside the host_lock as well.
Signed-off-by: Tyrel Datwyler
Reviewed-by: Brian King
---
The drivers queuecommand routine is still wrapped to hold the host lock
for the duration of the call. This will become problematic when moving
to multiple queues due to the lock contention preventing asynchronous
submissions to mulitple queues. There is no real legatimate reason to
hold the host
The ibmvfc driver in its current form relies heavily on the host_lock. This
patchset introduces a genric queue with its own queue lock and sent/free event
list locks. This generic queue allows the driver to decouple the primary queue
and future subordinate queues from the host lock reducing lock
On 12/1/20 2:34 PM, mgr...@linux.intel.com wrote:
> From: Srikanth Thokala
>
> Provide overview of XLink PCIe driver implementation
>
> Cc: linux-...@vger.kernel.org
> Reviewed-by: Mark Gross
> Signed-off-by: Srikanth Thokala
> ---
> Documentation/vpu/index.rst | 1 +
>
get_features ops of pci_epc_ops may return NULL, causing NULL pointer
dereference in pci_epf_test_bind function. Let us add a check for
pci_epc_feature pointer in pci_epf_test_bind before we access it to
avoid any such NULL pointer dereference and return -ENOTSUPP in case
pci_epc_feature is not
On Wed, Dec 16, 2020 at 9:55 AM Grzegorz Jaszczyk
wrote:
>
> Hi Rob,
>
> On Mon, 14 Dec 2020 at 23:58, Rob Herring wrote:
> >
> > On Fri, Dec 11, 2020 at 03:29:29PM +0100, Grzegorz Jaszczyk wrote:
> > > From: Suman Anna
> > >
> > > Add a YAML binding document for PRU consumers. The binding
Since outbound iATU permits size to be greater than
4GB for which the support is also available, allow
EP function to send u64 size instead of truncating
to u32.
Signed-off-by: Shradha Todi
---
drivers/pci/controller/dwc/pcie-designware.c | 2 +-
drivers/pci/controller/dwc/pcie-designware.h | 2
On Fri, Dec 18 2020 at 13:58, Dan Williams wrote:
> On Fri, Dec 18, 2020 at 1:06 PM Thomas Gleixner wrote:
>> kmap_local() is fine. That can work automatically because it's strict
>> local to the context which does the mapping.
>>
>> kmap() is dubious because it's a 'global' mapping as dictated
On 12/17/20 3:07 AM, John Garry wrote:
> References to old IO sched requests are currently cleared from the
> tagset when freeing those requests; switching elevator or changing
> request queue depth is such a scenario in which this occurs.
>
> However, this does not stop the potentially racy
On Thu, Dec 17, 2020 at 7:48 PM Liu Ying wrote:
>
> Hi,
>
> On Thu, 2020-12-17 at 12:50 -0600, Rob Herring wrote:
> > On Thu, 17 Dec 2020 17:59:23 +0800, Liu Ying wrote:
> > > This patch adds bindings for i.MX8qm/qxp pixel combiner.
> > >
> > > Signed-off-by: Liu Ying
> > > ---
> > >
On Fri, Dec 18, 2020 at 1:17 PM Alexandre Belloni
wrote:
>
> On 18/12/2020 16:58:56-0400, Jason Gunthorpe wrote:
> > On Fri, Dec 18, 2020 at 08:32:11PM +, Mark Brown wrote:
> >
> > > > So, I strongly suspect, MFD should create mfd devices on a MFD bus
> > > > type.
> > >
> > > Historically
Hi Arnd!
On 12/18/20 11:13 PM, John Paul Adrian Glaubitz wrote:
>> I've attached a patch for a partial revert of my original change, this
>> should still work with the final cleanup on top, but restore the loop
>> plus the local_irq_enable()/local_irq_disable() that I dropped from
>> the original
Hi!
> > > > > Patches are on top of Shawn's imx/defconfig
> > > >
> > > > Thanks for bringing support for your hardware to the mainline.
> > > >
> > > > Can I ask phone-de...@vger.kernel.org to be cc-ed for phone-related
> > > > changes?
> > >
> > > Good point. Done with v3.
> > >
> > > > How
On 18/12/2020, Sam Ravnborg wrote:
> The sun4m and sun4d based SPARC machines was very popular in the
> 90'ties and was then replaced by the more powerful sparc64
> class of machines.
> Today there is only Gentoo that to my best knowledge supports
> sparc32 and people have moved on to more
On 18/12/2020 20:37, Andy Shevchenko wrote:
> On Thu, Dec 17, 2020 at 11:43:31PM +, Daniel Scally wrote:
>> From: Heikki Krogerus
>>
>> This implements the remaining .graph_* callbacks in the
>> fwnode operations structure for the software nodes. That makes
>> the fwnode_graph*() functions
The following commit has been merged into the timers/urgent branch of tip:
Commit-ID: f6f5cd840ae782680c5e94048c72420e4e6857f9
Gitweb:
https://git.kernel.org/tip/f6f5cd840ae782680c5e94048c72420e4e6857f9
Author:Colin Ian King
AuthorDate:Thu, 17 Dec 2020 17:17:05
Hi Laurent
On 18/12/2020 16:02, Laurent Pinchart wrote:
> Hi Daniel,
>
> Thank you for the patch.
>
> On Thu, Dec 17, 2020 at 11:43:29PM +, Daniel Scally wrote:
>> Registering software_nodes with the .parent member set to point to a
>> currently unregistered software_node has the potential
On Thu, Dec 17, 2020 at 9:00 AM Thierry Reding wrote:
>
> On Tue, Nov 10, 2020 at 08:33:09PM +0100, Thierry Reding wrote:
> > On Fri, Nov 06, 2020 at 04:25:48PM +0100, Thierry Reding wrote:
> > > On Thu, Nov 05, 2020 at 05:47:21PM +, Robin Murphy wrote:
> > > > On 2020-11-05 16:43, Thierry
Hi Laurent - thanks for comments as always
On 18/12/2020 16:22, Laurent Pinchart wrote:
> Hi Daniel,
>
> Thank you for the patch.
>
> On Thu, Dec 17, 2020 at 11:43:31PM +, Daniel Scally wrote:
>> From: Heikki Krogerus
>>
>> This implements the remaining .graph_* callbacks in the
>> fwnode
Hi Arnd!
On 12/18/20 11:07 PM, Arnd Bergmann wrote:
> Sorry for causing this bug, and thank you for bisecting it
> down to my patch.
>
> Do you see any other strange behavior with that patch, or is
> this the only symptom you are aware of?
This seems to be the only issue I'm seeing so far.
1 - 100 of 712 matches
Mail list logo
