An MHI device is not necessarily associated with only channels as we can
have one associated with the controller itself. Hence, the chan_name
field within the mhi_device structure should instead be replaced with a
generic name to accurately reflect any type of MHI device.
Signed-off-by: Bhaumik
Device hardware specific information such as serial number and the OEM
PK hash can be read using BHI and saved on host to identify the
endpoint.
Signed-off-by: Bhaumik Bhatt
Reviewed-by: Jeffrey Hugo
---
drivers/bus/mhi/core/boot.c | 17 -
include/linux/mhi.h | 6
Interrupt is a required property according to SRC binding, add
it for SRC node.
Signed-off-by: Anson Huang
---
arch/arm/boot/dts/imx51.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/imx51.dtsi b/arch/arm/boot/dts/imx51.dtsi
index 92fbb90..3f1e913 100644
---
Interrupt is a required property according to SRC binding, add
it for SRC node.
Signed-off-by: Anson Huang
---
arch/arm/boot/dts/imx53.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/imx53.dtsi b/arch/arm/boot/dts/imx53.dtsi
index 8536f59..0d06dbd 100644
---
Introduce debugfs entries to show state, channel, and event ring
information. Add MHI state counters to keep track of the state changes
on the device and add a helper API mhi_to_physical() to see the physical
address from debugfs. Also, allow the host to trigger a device reset,
issue bus or device
Introduce sysfs entries to enable userspace clients the ability to read
the serial number and the OEM PK Hash values obtained from BHI. OEMs
need to read these device-specific hardware information values through
userspace for factory testing purposes and cannot be exposed via degbufs
as it may
Introduce independent bus and device voting mechanism for clients and save
hardware information from BHI.
Allow reading and modifying some MHI variables for debug, test, and
information purposes using debugfs.
Read values for device specific hardware information to be used by OEMs in
factory
Introduce a helper function to determine whether the device is in a
powered ON state and resides in one of the active MHI states. This will
allow for some use cases in reading debugfs entries.
Signed-off-by: Bhaumik Bhatt
Reviewed-by: Jeffrey Hugo
---
drivers/bus/mhi/core/internal.h | 5 +
Allow independent votes from clients such that they can choose to vote
for either the device or the bus or both. This helps in cases where the
device supports autonomous low power mode wherein it can move to M2
state without the need to notify the host. Clients can also vote only to
keep the
Convert the i.MX reset binding to DT schema format using json-schema.
Signed-off-by: Anson Huang
---
.../devicetree/bindings/reset/fsl,imx-src.txt | 49 --
.../devicetree/bindings/reset/fsl,imx-src.yaml | 58 ++
2 files changed, 58 insertions(+), 49
Fix the following sparse warning:
arch/arm/mach-zx/platsmp.c:41:13: warning: symbol 'zx_smp_prepare_cpus' was not
declared.
The zx_smp_prepare_cpus has only call site within platsmp.c
It should be static
Fixes: 71bc724300e6 ("ARM: zx: enable SMP and hotplug for zx296702")
Reported-by: Hulk
On 5/9/2020 2:37 AM, Stanley Chu wrote:
Change the WriteBooster policy to keep VCC on during
runtime suspend if available WriteBooster buffer is less
than 80%.
Signed-off-by: Stanley Chu
---
drivers/scsi/ufs/ufs-mediatek.c | 1 +
1 file changed, 1 insertion(+)
diff --git
Hi Rob,
On 2020/05/12 11:01, Rob Herring wrote:
On Tue, Apr 28, 2020 at 03:31:22PM +0900, Kunihiko Hayashi wrote:
Convert the UniPhier AVE4 controller binding to DT schema format.
This changes phy-handle property to required.
Signed-off-by: Kunihiko Hayashi
---
(snip)
+ phy-mode:
+
syzbot has found a reproducer for the following crash on:
HEAD commit:ac935d22 Add linux-next specific files for 20200415
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13a38f0a10
kernel config:
On Fri 08 May 13:41 PDT 2020, Sumit Semwal wrote:
> From: Nisha Kumari
>
> Qualcomm platforms have LAB(LCD AMOLED Boost)/IBB(Inverting Buck Boost)
> Regulators, labibb for short, which are used as power supply for
lowercase Regulators
> LCD Mode displays.
>
> This patch adds labibb regulator
On Mon, 11 May 2020 at 19:37, Oded Gabbay wrote:
>
> On Mon, May 11, 2020 at 12:11 PM Daniel Vetter wrote:
> >
> > It's the default.
> Thanks for catching that.
>
> >
> > Also so much for "we're not going to tell the graphics people how to
> > review their code", dma_fence is a pretty core piece
This replaces multiple open encoding (0x7) with ID_AA64MMFR0_PARANGE_MASK
thus cleaning the clutter. It modifies an existing ID_AA64MMFR0 helper and
introduces a new one i.e id_aa64mmfr0_iparange() and id_aa64mmfr0_parange()
respectively.
Cc: Catalin Marinas
Cc: Will Deacon
Cc: Marc Zyngier
On Mon, May 11, 2020 at 10:33:48AM -0700, Paul E. McKenney wrote:
> On Sun, May 10, 2020 at 04:21:02PM +0900, Akira Yokosawa wrote:
> > On Sat, 9 May 2020 12:43:30 +0900, Akira Yokosawa wrote:
> > > Hi Joel,
> > >
> > > Sorry for the late response but I've noticed some glitches.
> > >
> > > On
Hi,
Ping!
Thanks,
Xiao Yang
On 2020/2/26 9:08, Xiao Yang wrote:
> Avoid the following errors when building perf on i386:
> ---
> util/session.c: In function 'perf_session__process_compressed_event':
> util/session.c:91:11: error: format '%ld' expects
On Tue, Apr 28, 2020 at 04:16:48AM -0700, Sagar Shrikant Kadam wrote:
> Adding a OUI (Organizationally Unique Identifier) for VSC8541-01
> device to dt node requires a corresponding dt-binding entry as well
> so that checkpatch doesn't complain with a warning:
>
> DT compatible string
Fix the following sparse warning:
drivers/iommu/msm_iommu.c:37:1: warning: symbol 'msm_iommu_lock' was not
declared.
The msm_iommu_lock has only call site within msm_iommu.c
It should be static
Fixes: 0720d1f052dc ("msm: Add MSM IOMMU support")
Reported-by: Hulk Robot
Signed-off-by: Samuel
On Mon, May 11, 2020 at 04:40:52PM +0100, Qais Yousef wrote:
> RT tasks by default run at the highest capacity/performance level. When
> uclamp is selected this default behavior is retained by enforcing the
> requested uclamp.min (p->uclamp_req[UCLAMP_MIN]) of the RT tasks to be
>
On Tue, 12 May 2020 at 09:06, Ilia Mirkin wrote:
>
> On Mon, May 11, 2020 at 6:42 PM Lyude Paul wrote:
> > diff --git a/drivers/gpu/drm/nouveau/nouveau_connector.c
> > b/drivers/gpu/drm/nouveau/nouveau_connector.c
> > index 43bcbb6d73c4..6dae00da5d7e 100644
> > ---
Fix the following sparse warning:
drivers/soc/ti/knav_qmss_queue.c:412:23: warning: symbol 'knav_gp_range_ops'
was not declared.
The knav_acc_firmwares has only call site within knav_qmss_queue.c
It should be static
Fixes: 41f93af900a2 ("soc: ti: add Keystone Navigator QMSS driver")
On Tue, 28 Apr 2020 15:34:50 +0900, Kunihiko Hayashi wrote:
> Convert the UniPhier USB3-PHY controller for SS/HS to DT schema format.
>
> Signed-off-by: Kunihiko Hayashi
> ---
> .../phy/socionext,uniphier-usb3hs-phy.yaml | 104
> +
>
On Tue, 28 Apr 2020 15:34:49 +0900, Kunihiko Hayashi wrote:
> Convert the UniPhier USB2-PHY conroller to DT schema format.
>
> Signed-off-by: Kunihiko Hayashi
> ---
> .../bindings/phy/socionext,uniphier-usb2-phy.yaml | 85
> ++
>
Mission mode transition is handled by state worker thread but
power off is not. There is a possibility while mission mode
transition is in progress which calls MHI client driver probe,
power off is issued by MHI controller. This results into client
driver probe and remove running in parallel and
Driver continues handling of BHI interrupt even if MHI register access
is not allowed. By doing so it calls the status call back and performs
early notification for the MHI client. This is not needed when MHI
register access is not allowed. Hence skip the handling in this case and
return. Also add
Remove the system error worker thread and instead have the
execution environment worker handle that transition to serialize
processing and avoid any possible race conditions during
shutdown.
Signed-off-by: Hemant Kumar
Reviewed-by: Jeffrey Hugo
---
drivers/bus/mhi/core/init.c | 2 +-
On Tue, 28 Apr 2020 15:34:48 +0900, Kunihiko Hayashi wrote:
> Convert the UniPhier PCIe-PHY controller to DT schema format.
>
> Signed-off-by: Kunihiko Hayashi
> ---
> .../bindings/phy/socionext,uniphier-pcie-phy.yaml | 77
> ++
>
Patches are addressing MHI core driver bug fixes. Patches tested on
arm64 and x86 platforms.
Hemant Kumar (5):
bus: mhi: core: Remove the system error worker thread
bus: mhi: core: Handle disable transitions in state worker
bus: mhi: core: Skip handling BHI irq if MHI reg access is not
Devices that support RDDM do not require processing SYS_ERROR as it is
deemed redundant. Avoid SYS_ERROR processing if RDDM is supported by
the device.
Signed-off-by: Hemant Kumar
Reviewed-by: Jeffrey Hugo
---
drivers/bus/mhi/core/main.c | 11 ---
1 file changed, 8 insertions(+), 3
Take write lock only to protect db_mode member of mhi channel.
This allows rest of the mhi channels to just take read lock which
fine grains the locking. It prevents channel readers to starve if
they try to enter critical section after a writer.
Signed-off-by: Hemant Kumar
---
On Tue, Apr 28, 2020 at 03:31:22PM +0900, Kunihiko Hayashi wrote:
> Convert the UniPhier AVE4 controller binding to DT schema format.
> This changes phy-handle property to required.
>
> Signed-off-by: Kunihiko Hayashi
> ---
> .../bindings/net/socionext,uniphier-ave4.txt | 64
This validates hypervisor capabilities like VMID width, IPA range for any
hot plug CPU against system finalized values. KVM's view of the IPA space
is used while allowing a given CPU to come up. While here, it factors out
get_vmid_bits() for general use.
Cc: Catalin Marinas
Cc: Will Deacon
Cc:
On 2020/5/12 6:11, Jaegeuk Kim wrote:
> On 05/11, Chao Yu wrote:
>> On 2020/5/10 3:03, Jaegeuk Kim wrote:
>>> On 05/09, Chao Yu wrote:
On 2020/5/9 0:10, Jaegeuk Kim wrote:
> Hi Sayali,
>
> In order to address the perf regression, how about this?
>
> >From
On Mon, 27 Apr 2020 21:32:24 +0200, Geert Uytterhoeven wrote:
> Convert the Renesas OS Timer (OSTM) Device Tree binding documentation to
> json-schema.
>
> Document missing properties.
>
> Signed-off-by: Geert Uytterhoeven
> ---
> For a clean dtbs_check, this depends on "[PATCH] ARM: dts:
Fix the following sparse warnings:
drivers/usb/gadget/udc/atmel_usba_udc.c:188:30: warning: symbol
'queue_dbg_fops' was not declared.
drivers/usb/gadget/udc/atmel_usba_udc.c:196:30: warning: symbol 'regs_dbg_fops'
was not declared.
queue_dbg_fops and regs_dbg_fops have only call within
On Mon, 27 Apr 2020 18:54:03 +0530, Jishnu Prakash wrote:
> Add documentation for PMIC7 ADC peripheral.
> For the PMIC7-type PMICs, ADC peripheral is present in HW for the
> following PMICs: PMK8350, PM8350, PM8350b, PMR735a and PMR735b.
> Of these, only the ADC peripheral on PMK8350 is exposed
On 5/7/20 9:19 AM, Jeffrey Hugo wrote:
The MHI device may be in the syserr state when we attempt to init it in
power_up(). Since we have no local state, the handling is simple -
reset the device and wait for it to transition out of the reset state.
Signed-off-by: Jeffrey Hugo
On Tue, 05 May 2020 15:41:22 +0200
Thomas Gleixner wrote:
> The preempt_enable_notrace() ASM thunk is called from tracing, entry code
> RCU and other places which are already in or going to be in the noinstr
> section which protects sensitve code from being instrumented.
>
> Calls out of these
On Fri, May 8, 2020 at 8:47 AM Etienne Carriere
wrote:
>
> From: Etienne Carriere
>
> Introduce boolean property st,non-secure-otp for OTP data located
> in a factory programmed area that only secure firmware can access
> by default and that shall be reachable from the non-secure world.
>
>
On 2020/5/11 14:15, Konstantin Khlebnikov wrote:
> This reserved space isn't committed yet but cannot be used for
> allocations. For userspace it has no difference from used space.
>
> See the same fix in ext4 commit f06925c73942 ("ext4: report delalloc
> reserve as non-free in statfs for project
On Mon, 27 Apr 2020 18:54:02 +0530, Jishnu Prakash wrote:
> Convert the adc bindings from .txt to .yaml format.
>
> Signed-off-by: Jishnu Prakash
> ---
> .../devicetree/bindings/iio/adc/qcom,spmi-vadc.txt | 173 --
> .../bindings/iio/adc/qcom,spmi-vadc.yaml | 252
>
On Fri, 8 May 2020 17:10:09 -0700
Andy Lutomirski wrote:
> On Tue, May 5, 2020 at 7:14 AM Thomas Gleixner wrote:
> >
> > The preempt_enable_notrace() ASM thunk is called from tracing, entry code
> > RCU and other places which are already in or going to be in the noinstr
> > section which
On Fri 08 May 13:41 PDT 2020, Sumit Semwal wrote:
> From: Nisha Kumari
>
> Adding the devicetree binding for labibb regulator.
>
> Signed-off-by: Nisha Kumari
> Signed-off-by: Sumit Semwal
Sorry, I missed this when we talked about it. But please rewrite this in
yaml.
>
> --
> v2: updated
Hi Jaegeuk,
I think we need this patch in order to avoid writebacking incomplete data
compressed by zstd.
On 2020/5/8 9:16, Chao Yu wrote:
> During zstd compression, ZSTD_endStream() may return non-zero value
> because distination buffer is full, but there is still compressed data
> remained in
On Mon, 11 May 2020 21:55:33 +0200, Lubomir Rintel wrote:
> This describes the bindings for a controller that generates master and bit
> clocks for the I2S interface.
>
> Signed-off-by: Lubomir Rintel
> ---
> .../clock/marvell,mmp2-audio-clock.yaml | 73 +++
>
Xiaoliang Yang writes:
> VSC9959 hardware support the Credit Based Shaper(CBS) which part
> of the IEEE-802.1Qav. This patch support sch_cbs set for VSC9959.
>
> Signed-off-by: Xiaoliang Yang
> ---
> drivers/net/dsa/ocelot/felix_vsc9959.c | 52 +-
> 1 file changed, 51
Fix sparse warning:
arch/arm/mach-oxnas/platsmp.c:30:12: warning: symbol 'ox820_boot_secondary' was
not declared. Should it be static?
Reported-by: Hulk Robot
Signed-off-by: Ma Feng
---
arch/arm/mach-oxnas/platsmp.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
On Thu 07 May 14:34 PDT 2020, Douglas Anderson wrote:
> The ti-sn65dsi86 MIPI DSI to eDP bridge chip has 4 pins on it that can
> be used as GPIOs in a system. Each pin can be configured as input,
> output, or a special function for the bridge chip. These are:
> - GPIO1: SUSPEND Input
> - GPIO2:
On Fri, 8 May 2020 15:45:27 +0200, Etienne Carriere wrote:
> From: Etienne Carriere
>
> Introduce boolean property st,non-secure-otp for OTP data located
> in a factory programmed area that only secure firmware can access
> by default and that shall be reachable from the non-secure world.
>
>
Hi all,
On Fri, 8 May 2020 04:54:02 +0530 Madhuparna Bhowmik
wrote:
>
> On Thu, May 07, 2020 at 08:50:55AM -0400, Qian Cai wrote:
> >
> >
> > > On May 7, 2020, at 5:32 AM, Dmitry Vyukov wrote:
> > >
> > > On Thu, May 7, 2020 at 11:26 AM syzbot
> > > wrote:
> > >>
> > >> Hello,
> > >>
On Thu 07 May 14:35 PDT 2020, Douglas Anderson wrote:
> We don't have the HPD line hooked up to the bridge chip. Add it as
> suggested in the patch ("dt-bindings: drm/bridge: ti-sn65dsi86:
> Document no-hpd").
>
> NOTE: this patch isn't expected to have any effect but just keeps us
> cleaner
On Mon 11 May 09:29 PDT 2020, Srinivas Kandagatla wrote:
> fastrpc_invoke_ctx can have refcount of 2 in error path where
> rpmsg_send() fails to send invoke message. decrement the refcount
> properly in the error path to fix this leak.
>
> This also fixes below static checker warning:
>
>
On Sun, May 10, 2020 at 9:47 PM David Laight wrote:
>
> From: Joe Perches
> > Sent: 08 May 2020 16:06
> > On Fri, 2020-05-08 at 13:49 +0200, Arnd Bergmann wrote:
> > > Personally, I'm more interested in improving compile speed of the kernel
> >
> > Any opinion on precompiled header support?
>
>
Am Montag, 11. Mai 2020, 23:36:05 CEST schrieb Rob Herring:
> On Fri, Apr 24, 2020 at 05:11:05PM +0200, Johan Jonker wrote:
> > The defines RK_GPIO0, RK_GPIO1, RK_GPIO2, RK_GPIO3,
> > RK_GPIO4 and RK_GPIO6 are no longer used. Mark them as
> > "deprecated" to prevent that someone start using them
On Tue, Apr 21, 2020 at 10:14:25AM +0200, Alexander Potapenko wrote:
> > Not lately and I would also like to hear the details; which regset it is?
> > Should be reasonably easy to find - just memset() the damn thing to
> > something
> > recognizable, do whatever triggers that KMSAN report and
On Tue, May 12, 2020 at 12:17:03AM +, Luis Chamberlain wrote:
> On Mon, May 11, 2020 at 07:59:14PM -0400, Rafael Aquini wrote:
> > On Mon, May 11, 2020 at 11:10:45PM +, Luis Chamberlain wrote:
> > > On Mon, May 11, 2020 at 05:59:04PM -0400, Rafael Aquini wrote:
> > > > diff --git
On Mon 11 May 09:27 PDT 2020, Srinivas Kandagatla wrote:
> fastrpc_channel_ctx is not freed if misc_register() fails, this would
> lead to a memory leak. Fix this leak by adding kfree in misc_register()
> error path.
>
> Fixes: 278d56f970ae ("misc: fastrpc: Reference count channel context")
>
Current qi_submit_sync() only supports single invalidation descriptor
per submission and appends wait descriptor after each submission to
poll the hardware completion. This extends the qi_submit_sync() helper
to support multiple descriptors, and add an option so that the caller
could specify the
Export invalidation queue internals of each iommu device through the
debugfs.
Example of such dump on a Skylake machine:
$ sudo cat /sys/kernel/debug/iommu/intel/invalidation_queue
Invalidation queue on IOMMU: dmar1
Base: 0x1672c9000 Head: 80Tail: 80
Index qw0
IOTLB flush already included in the PASID tear down and the page request
drain process. There is no need to flush again.
Signed-off-by: Jacob Pan
Signed-off-by: Lu Baolu
Reviewed-by: Kevin Tian
---
drivers/iommu/intel-svm.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff
When a PASID is stopped or terminated, there can be pending PRQs
(requests that haven't received responses) in remapping hardware.
This adds the interface to drain page requests and call it when a
PASID is terminated.
Signed-off-by: Jacob Pan
Signed-off-by: Liu Yi L
Signed-off-by: Lu Baolu
---
When a PASID is used for SVA by the device, it's possible that the PASID
entry is cleared before the device flushes all ongoing DMA requests. The
IOMMU should tolerate and ignore the non-recoverable faults caused by the
untranslated requests from this device.
For example, when an exception
When a PASID is stopped or terminated, there can be pending PRQs
(requests that haven't received responses) in the software and
remapping hardware. The pending page requests must be drained
so that the pasid could be reused. The chapter 7.10 in the VT-d
specification specifies the software steps
On 5/9/2020 19:01, Thomas Bogendoerfer wrote:
> Instead of including all Platform files, we simply include the
> needed one and avoid clashes with makefile variables.
>
> Signed-off-by: Thomas Bogendoerfer
> ---
> arch/mips/Kbuild.platforms | 73
> +---
On Mon, May 11, 2020 at 05:24:09PM -0700, Doug Berger wrote:
> This commit introduces the phy_set_pause function to the phylib as
> a helper to support the set_pauseparam ethtool method.
>
> It is hoped that the new behavior introduced by this function will
> be widely embraced and the
From: Ramuthevar Vadivel Murugan
Add dt-bindings documentation for Cadence-QSPI controller to support
spi based flash memories.
Signed-off-by: Ramuthevar Vadivel Murugan
---
.../devicetree/bindings/mtd/cadence-quadspi.txt| 67 ---
.../devicetree/bindings/spi/cdns,qspi-nor.yaml
On Mon, May 11, 2020 at 05:24:07PM -0700, Doug Berger wrote:
> A comment in uapi/linux/ethtool.h states "Drivers should reject a
> non-zero setting of @autoneg when autoneogotiation is disabled (or
> not supported) for the link".
>
> That check should be added to phy_validate_pause() to
On Mon, May 11, 2020 at 6:05 PM Linus Torvalds
wrote:
> There's a reason -O3 isn't even offered as an option.
>
> Maybe things have changed, and maybe they've improved. But I'd like to
> see actual numbers for something like this.
>
> Not inlining as aggressively is not necessarily a bad thing.
On 2020-05-11 17:30, Bjorn Andersson wrote:
On Mon 11 May 17:11 PDT 2020, risha...@codeaurora.org wrote:
On 2020-05-07 13:21, Bjorn Andersson wrote:
> On Thu 16 Apr 11:38 PDT 2020, Rishabh Bhatnagar wrote:
>
> > This patch adds the inline coredump functionality. The current
> > coredump
On Mon 11 May 14:27 PDT 2020, Konrad Dybcio wrote:
> From: Vincent Knecht
>
> This patch adds missing SoC IDs for MSM8936/39 and
> their APQ variants.
>
> Signed-off-by: Vincent Knecht
> Signed-off-by: Konrad Dybcio
Applied, thank you.
> ---
> Changes since v1:
> - Add a proper
On Mon, May 11, 2020 at 09:55:16AM +0800, Xiaoming Ni wrote:
> On 2020/5/11 9:11, Stephen Rothwell wrote:
> > Hi all,
> >
> > Today's linux-next merge of the vfs tree got a conflict in:
> >
> >kernel/sysctl.c
> >
> > between commit:
> >
> >b6522fa409cf ("parisc: add sysctl file
Hi all,
Commits
ee8ad8190cb1 ("vfs, fsinfo: Add an RCU safe per-ns mount list")
a627d57b0248 ("fsinfo: Add an attribute that lists all the visible mounts in
a namespace")
are missing a Signed-off-by from their author and committer.
--
Cheers,
Stephen Rothwell
pgpfV6qSnLyn_.pgp
On Mon 11 May 17:11 PDT 2020, risha...@codeaurora.org wrote:
> On 2020-05-07 13:21, Bjorn Andersson wrote:
> > On Thu 16 Apr 11:38 PDT 2020, Rishabh Bhatnagar wrote:
> >
> > > This patch adds the inline coredump functionality. The current
> > > coredump implementation uses vmalloc area to copy
Upstream commit 051a2d3e59e51ae49fd56aef34e472832897ce46.
Use '%% " _ASM_CX"' instead of '%0' to dereference RCX, i.e. the
'struct vcpu_vmx' pointer, in the VM-Enter asm blobs of vmx_vcpu_run()
and nested_vmx_check_vmentry_hw(). Using the symbolic name means that
adding/removing an output
A simple fix for a null pointer dereference in vmx_vcpu_run() with an
ugly-but-safe prereq patch.
The even uglier ASM_CALL_CONSTRAINT is gone in v2 as I finally figured
out why vmx_return was undefined: GCC dropped the entire asm blob because
all outputs were deemed unused.
v2:
- Document why
Based on upstream commit f3689e3f17f064fd4cd5f0cb01ae2395c94f39d9.
Save RCX, RDX and RSI to fake outputs to coerce the compiler into
treating them as clobbered. RCX in particular is likely to be reused by
the compiler to dereference the 'struct vcpu_vmx' pointer, which will
result in a null
Hi Robert,
On Mon, May 11, 2020 at 01:03:49PM +0200, Robert Foss wrote:
> Add match table, enable ov8856_probe() to support
> both ACPI and DT modes.
>
> ACPI and DT modes are primarily distinguished from
> by checking for ACPI mode and by having resource like
> be NULL.
>
> Signed-off-by:
This commit introduces a new parameter to linkmode_set_pause to
provide a mechanism to specify two alternative mappings of the
pause parameters for advertisement by the PHY.
An argument is made that the advertisement through Pause and
AsymPause of the desired Rx and Tx pause frame use should be
This commit extends the supported ethtool operations to allow MAC
level flow control to be configured for the bcmgenet driver. It
provides an example of how the new phy_set_pause function and the
phy_validate_pause function can be used to configure the desired
PHY advertising as well as how the
A comment in uapi/linux/ethtool.h states "Drivers should reject a
non-zero setting of @autoneg when autoneogotiation is disabled (or
not supported) for the link".
That check should be added to phy_validate_pause() to consolidate
the code where possible.
Fixes: 22b7d29926b5 ("net: ethernet: Add
This commit set extends the implementation introduced by
commit 5652b46e4e80 ("Merge branch 'Pause-updates-for-phylib-and-phylink'")
to support the less problematic behavior alluded to by Russell King's
comment in commit f904f15ea9b5 ("net: phylink: allow ethtool -A to
change flow control
This commit introduces the phy_set_pause function to the phylib as
a helper to support the set_pauseparam ethtool method.
It is hoped that the new behavior introduced by this function will
be widely embraced and the phy_set_sym_pause and phy_set_asym_pause
functions can be deprecated. Those
On Fri, May 08, 2020 at 10:47:20AM +1000, Stephen Rothwell wrote:
> After merging the nfsd tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> kernel/trace/trace_hwlat.c:329:12: error: conflicting types for 'kthread_fn'
> 329 | static int kthread_fn(void *data)
>
On Fri, May 08, 2020 at 09:32:59AM +0800, Xiongfeng Wang wrote:
> When I cat parameter '/sys/module/sunrpc/parameters/pool_mode', it
> displays as follows. It is better to add a newline for easy reading.
Applying for 5.8. I assume Trond's getting the other patch.
--b.
>
> [root@hulk-202 ~]#
I'm not exactly an expert on this, but looks alright to me.
Acked-by: Roland Scheidegger
Am 05.05.20 um 10:46 schrieb Marek Szyprowski:
> The Documentation/DMA-API-HOWTO.txt states that dma_map_sg returns the
> numer of the created entries in the DMA address space. However the
> subsequent calls
On Mon, May 11, 2020 at 07:59:14PM -0400, Rafael Aquini wrote:
> On Mon, May 11, 2020 at 11:10:45PM +, Luis Chamberlain wrote:
> > On Mon, May 11, 2020 at 05:59:04PM -0400, Rafael Aquini wrote:
> > > diff --git a/kernel/sysctl.c b/kernel/sysctl.c
> > > index 8a176d8727a3..f0a4fb38ac62 100644
>
On 2020-05-07 13:21, Bjorn Andersson wrote:
On Thu 16 Apr 11:38 PDT 2020, Rishabh Bhatnagar wrote:
This patch adds the inline coredump functionality. The current
coredump implementation uses vmalloc area to copy all the segments.
But this might put a lot of strain on low memory targets as the
On Tue 21 Apr 08:43 PDT 2020, Paul Cercueil wrote:
> Hi Bjorn,
>
> Le dim. 19 avril 2020 à 23:37, Bjorn Andersson
> a écrit :
> > On Fri 17 Apr 10:00 PDT 2020, Paul Cercueil wrote:
> >
> > > This driver is used to boot, communicate with and load firmwares to
> > > the
> > > MIPS co-processor
On Tue, 12 May 2020 at 02:54, David Miller wrote:
>
> From: Xiaoliang Yang
> Date: Mon, 11 May 2020 13:43:31 +0800
>
> > @@ -710,7 +714,7 @@ static void felix_port_policer_del(struct dsa_switch
> > *ds, int port)
> > ocelot_port_policer_del(ocelot, port);
> > }
> >
> > -static const
On Mon, May 11, 2020 at 5:04 PM Linus Torvalds
wrote:
>
> Not inlining as aggressively is not necessarily a bad thing. It can
> be, of course. But I've actually also done gcc bugreports about gcc
> inlining too much, and generating _worse_ code as a result (ie
> inlinging things that were behind
Hi,
The following are two patches that deal with removing the tasklist_lock
entirely in
getpriority(2), and reducing the scope of it in setpriority(2). This also aligns
somewhat to what we already do with io priorities - although there both set and
get
rely entirely on rcu.
Details in the
Currently the tasklist_lock is shared mainly in order to observe
the list atomically for the PRIO_PGRP and PRIO_USER cases, as
the actual lookups are already rcu-safe, providing a stable task
pointer. By removing the lock, we can race with:
(i) fork (insertion), but this is benign as the child's
This option does not iterate the tasklist and we already have
an rcu aware stable pointer. Also, the nice value is not serialized
by this lock. Reduce the scope of this lock to just PRIO_PGRP
and PRIO_USER - which need to to set the priorities atomically
to the list of tasks, at least vs fork().
On Mon, 11 May 2020, Markus Elfring wrote:
> > If you can't determine when the bug was introduced,
>
> I might be able to determine also this information.
>
This is tantamount to an admission of duplicity.
>
> > how can you criticise a patch for the lack of a Fixes tag?
>
> I dared to
On Mon, May 11, 2020 at 2:57 PM Jason A. Donenfeld wrote:
>
> GCC 10 appears to have changed -O2 in order to make compilation time
> faster when using -flto, seemingly at the expense of performance, in
> particular with regards to how the inliner works. Since -O3 these days
> shouldn't have the
From: Al Viro
Date: Mon, 11 May 2020 05:43:28 +0100
> Assorted uaccess-related work in net/*. First, there's
> getting rid of compat_alloc_user_space() mess in MCAST_...
> [gs]etsockopt() - no need to play with copying to/from temporary
> object on userland stack, etc., when
From: Christoph Hellwig
Date: Mon, 11 May 2020 13:59:10 +0200
> this series replace the msg_control in the kernel msghdr structure
> with an anonymous union and separate fields for kernel vs user
> pointers. In addition to helping a bit with type safety and reducing
> sparse warnings, this also
101 - 200 of 1519 matches
Mail list logo
