From: Alex Deucher
[ Upstream commit dc14eb12f6bb3e779c5461429c1889a339c67aab ]
Add missing power_average to visible check for power
attributes for APUs. Was missed before.
Reviewed-by: Evan Quan
Signed-off-by: Alex Deucher
Signed-off-by: Sasha Levin
---
From: Jose Abreu
[ Upstream commit e2cd682deb231ba6f80524bb84e57e7138261149 ]
In stmmac xmit callback we use a different flow for TSO packets but TSO
xmit callback is not disabling the EEE mode.
Fix this by disabling earlier the EEE mode, i.e. before calling the TSO
xmit callback.
From: Lubomir Rintel
[ Upstream commit 2380a22b60ce6f995eac806e69c66e397b59d045 ]
Resetting bit 4 disables the interrupt delivery to the "secure
processor" core. This breaks the keyboard on a OLPC XO 1.75 laptop,
where the firmware running on the "secure processor" bit-bangs the
PS/2 protocol
From: Paul Cercueil
[ Upstream commit 70999ec1c9d3f783a7232973cfc26971e5732758 ]
The interrupt number set in the devicetree node of the DMA driver was
wrong.
Signed-off-by: Paul Cercueil
Signed-off-by: Paul Burton
Cc: Rob Herring
Cc: Mark Rutland
Cc: Ralf Baechle
Cc: James Hogan
Cc:
From: Marc Zyngier
[ Upstream commit 45725e0fc3e7fe52fedb94f59806ec50e9618682 ]
In the unlikely event that we cannot find any available LPI in the
system, we should gracefully return an error instead of carrying
on with no LPI allocated at all.
Fixes: 38dd7c494cf6 ("irqchip/gic-v3-its: Drop
From: Jakub Sitnicki
[ Upstream commit 1d79895aef18fa05789995d86d523c9b2ee58a02 ]
Despite having stopped the parser, we still need to deinitialize it
by calling strp_done so that it cancels its work. Otherwise the worker
thread can run after we have freed the parser, and attempt to access
its
On Thu, Feb 28, 2019 at 04:14:50PM +0100, Paolo Bonzini wrote:
> On 28/02/19 16:08, Greg Kroah-Hartman wrote:
> > debugfs can now report an error code if something went wrong instead of
> > just NULL. So if the return value is to be used as a "real" dentry, it
> > needs to be checked if it is an
From: Felix Fietkau
[ Upstream commit 7d652669b61d702c6e62a39579d17f6881670ab6 ]
With the addition of TXQ stats in the per-tid statistics the struct
station_info grew significantly. This resulted in stack size warnings
due to the structure itself being above the limit for the warnings.
To work
From: Alexey Khoroshilov
[ Upstream commit 512e6fb589bc18f9321457632e89b95017447db9 ]
If clk_prepare_enable() fails in dwc3_exynos_probe() or in
dwc3_exynos_resume(), exynos->clks[0] is left undisabled
because of usage preincrement in while condition.
Found by Linux Driver Verification project
From: Anders Roxell
[ Upstream commit f2105d42597f4d10e431b195d69e96dccaf9b012 ]
Fix link errors when CONFIG_FSL_USB2_OTG is enabled and USB_OTG_FSM is
set to module then the following link error occurs.
aarch64-linux-gnu-ld: drivers/usb/phy/phy-fsl-usb.o: in function
`fsl_otg_ioctl':
From: Arthur Demchenkov
[ Upstream commit ac9c908eecde3ed252cb1d67fc79b3c1346f76bc ]
Wrong polarity of card detect GPIO pin leads to the system not
booting from external mmc, if the back cover of N900 is closed.
When the cover is open the system boots fine.
This wasn't noticed before, because
From: Heiko Schocher
[ Upstream commit 063c20e12f8bbbc10cabc2413606b140085beb62 ]
cd pin on mmc1 is GPIO_ACTIVE_LOW not GPIO_ACTIVE_HIGH
Fixes: e63201f19438 ("mmc: omap_hsmmc: Delete platform data GPIO CD and WP")
Signed-off-by: Heiko Schocher
Signed-off-by: Tony Lindgren
Signed-off-by:
On Thu, Feb 28, 2019 at 02:52:31PM +0100, Flavio Suligoi wrote:
> Sometimes, in some embedded systems boards (i.e. ARM boards),
> the NVM eeprom is not mounted, to save cost and space.
>
> In this case it is necessary to bypass the NVM management
> and directly force the MAC address using a
From: Srinivas Kandagatla
[ Upstream commit 2a81efb0de0e33f2d2c83154af0bd3ce389b3269 ]
Add compatible to gicv3 node to enable quirk required to restrict writing
to GICR_WAKER register which is restricted on msm8996 SoC in Hypervisor.
With this quirk MSM8996 can at least boot out of mainline,
From: Yafang Shao
[ Upstream commit c9e4576743eeda8d24dedc164d65b78877f9a98c ]
When sock recvbuff is set by bpf_setsockopt(), the value must by
limited by rmem_max. It is the same with sendbuff.
Fixes: 8c4b4c7e9ff0 ("bpf: Add setsockopt helper function to bpf")
Signed-off-by: Yafang Shao
From: Ulf Hansson
[ Upstream commit 13e62626c578d9889ebbda7c521be5adff9bef8e ]
During "wlan-up", we are programming the FW into the WiFi-chip. However,
re-programming the FW doesn't work, unless a power cycle of the WiFi-chip
is made in-between the programmings.
To conform to this requirement
From: Paolo Abeni
[ Upstream commit b0ca5ecb8e2279d706261f525f1bd0ba9e3fe800 ]
When updating a percpu map, bpftool currently copies the provided
value only into the first per CPU copy of the specified value,
all others instances are left zeroed.
This change explicitly copies the user-provided
From: Martin Blumenstingl
[ Upstream commit 8615f5596335db0978cea593dcd0070dc5f8b116 ]
After commit 89a5e15bcba87d ("gpio/mmc/of: Respect polarity in the device
tree") SD cards are not detected anymore.
The CD GPIO is "active low" on the MXIII-Plus. The MMC dt-bindings
specify: "[...] using
From: Geert Uytterhoeven
[ Upstream commit 97f26702bc95b5c3a72671d5c6675e4d6ee0a2f4 ]
SCIF2 on R-Car M3-W can be used with both DMAC1 and DMAC2.
Fixes: dbcae5ea4bd27409 ("arm64: dts: r8a7796: Enable SCIF DMA")
Signed-off-by: Geert Uytterhoeven
Signed-off-by: Simon Horman
Signed-off-by: Sasha
From: Anson Huang
[ Upstream commit ba0f4560526ba19300c07ed5a3c1df7592815dc6 ]
i.MX6SX has same GPT type as i.MX6DL, in GPT driver, it uses
below TIMER_OF_DECLARE, so the backward compatible should be
"fsl,imx6dl-gpt", correct it.
TIMER_OF_DECLARE(imx6sx_timer, "fsl,imx6sx-gpt",
From: Aaro Koskinen
[ Upstream commit 8443e4843e1c2594bf5664e1d993a1be71d1befb ]
Commit a758f50f10cf ("mtd: onenand: omap2: Configure driver from DT")
started using DT specified timings for GPMC, and as a result the
OneNAND stopped working on N950/N9 as we had wrong values in the DT.
Fix by
From: "Eric W. Biederman"
[ Upstream commit ee17e5d6201c66492a0e8053190fca2ed2b8457d ]
Eric Biggers reported:
> The following commit, which went into v4.20, introduced undefined behavior
> when
> sys_rt_sigqueueinfo() is called with sig=0:
>
> commit 4ce5f9c9e7546915c559ffae594e6d73f918db00
>
From: Martin Blumenstingl
[ Upstream commit 3fb348e030319f20ebbde082a449d4bf8a96f2fd ]
After commit 89a5e15bcba87d ("gpio/mmc/of: Respect polarity in the device
tree") SD cards are not detected anymore.
The CD GPIO is "active low" on Odroid-C1. The MMC dt-bindings specify:
"[...] using the
From: Madalin Bucur
[ Upstream commit 89857a8a5c89a406b967ab2be7bd2ccdbe75e73d ]
By clearing all interrupt sources, not only those that
already occurred, the existing code may acknowledge by
mistake interrupts that occurred after the code checks
for them.
Signed-off-by: Madalin Bucur
From: Tony Lindgren
[ Upstream commit ef4a55b9197a8f844ea0663138e902dcce3e2f36 ]
We're now getting the following error:
genirq: Setting trigger mode 1 for irq 230 failed
(regmap_irq_set_type+0x0/0x15c)
cpcap-usb-phy cpcap-usb-phy.0: could not get irq dp: -524
Cc: Sebastian Reichel
debugfs can now report an error code if something went wrong instead of
just NULL. So if the return value is to be used as a "real" dentry, it
needs to be checked if it is an error before dereferencing it.
This is now happening because of ff9fb72bc077 ("debugfs: return error
values, not NULL").
From: Martin Blumenstingl
[ Upstream commit c8bfe65fb1fb7a43d766df1dfa379406112cba61 ]
After commit 89a5e15bcba87d ("gpio/mmc/of: Respect polarity in the device
tree") SD cards are not detected anymore.
The CD GPIO is "active low" on the EC-100. The MMC dt-bindings specify:
"[...] using the
On 2/28/19 4:42 AM, Christian Borntraeger wrote:
On 27.02.2019 19:00, Tony Krowiak wrote:
On 2/27/19 3:09 AM, Pierre Morel wrote:
On 26/02/2019 16:47, Tony Krowiak wrote:
On 2/26/19 6:47 AM, Pierre Morel wrote:
On 25/02/2019 19:36, Tony Krowiak wrote:
On 2/22/19 10:29 AM, Pierre Morel
From: Yazen Ghannam
AMD systems may support Chip Select interleaving. However, on Family
17h+ this was not taken into account when printing the Chip Select
sizes.
Add support to detect if Chip Selects are interleaved on Family 17h+,
and adjust the sizes accordingly.
Signed-off-by: Yazen
From: Yazen Ghannam
The struct chip_select array that's used for saving Chip Select bases
and masks is fixed at length of two. There should be one struct
chip_select for each controller, so this array should be increased to
support systems that may have more than two controllers.
Increase the
On 2/28/19 6:03 AM, Christian Borntraeger wrote:
On 28.02.2019 10:42, Christian Borntraeger wrote:
[...]
Okay, let's go back to the genesis of this discussion; namely, my
suggestion about moving the fc == 0x03 check into the hook code. If
the vfio_ap module is not loaded, there will be no
From: Yazen Ghannam
The first few models of Family 17h all had 2 Unified Memory Controllers
per Die, so this was treated as a fixed value. However, future systems
may have more Unified Memory Controllers per Die.
Related to this, the channel number and base address of a Unified Memory
From: Yazen Ghannam
Future AMD systems may support x16 symbol sizes.
Recognize if a system is using x16 symbol size. Also, simplify the print
statement.
Note that a x16 syndrome vector table is not necessary like with x4 or
x8. This is because systems that support x16 symbol sizes will be SMCA
From: Yazen Ghannam
Define and use a macro for looping over the number of Unified Memory
Controllers.
No functional change.
Signed-off-by: Yazen Ghannam
---
Link:
https://lkml.kernel.org/r/20190226172532.12924-3-yazen.ghan...@amd.com
v2->v3:
* Apply V2 Patch 3 before V2 Patch 2.
v1->v2:
*
From: Yazen Ghannam
Add the new Family 17h Model 30h PCI IDs to the AMD64 EDAC module.
This also fixes a probe failure that appeared when some other PCI IDs
for Family 17h Model 30h were added to the AMD NB code.
Fixes: be3518a16ef2 (x86/amd_nb: Add PCI device IDs for family 17h, model 30h)
On Thu, Feb 28, 2019 at 04:30:26PM +0100, Greg KH wrote:
> On Thu, Feb 28, 2019 at 10:00:54AM -0500, Joel Fernandes wrote:
> > > Hmm, isn't it easier to add kernel-headers package on Android?
> >
> > I have already been down that road. In the Android ecosystem, the Android
> > teams only provide
On Thu, Feb 28, 2019 at 12:49 AM Matti Vaittinen
wrote:
>
> Hello Rob, All
>
> Sorry for long delay - I was ill for a few days. Back at the business
> now =)
>
> Rob, maybe dropping the RFC tag has messed your book keeping? This
> is the latest version:
>
perf c2c report fails if system has empty numa node(0 cpus):
$ lscpu
NUMA node0 CPU(s):
NUMA node1 CPU(s): 0-4
$ sudo ./perf c2c report
node/cpu topology bugFailed setup nodes
Fix this.
Reported-by: Nageswara R Sastry
Signed-off-by: Ravi Bangoria
---
tools/perf/util/cpumap.c
On 28/02/2019 14:59, Ulf Hansson wrote:
> Instead of iterating through all the state nodes in DT, to find out how
> many states that needs to be allocated, let's use the number already known
> by the cpuidle driver. In this way we can drop the iteration altogether.
>
> Signed-off-by: Ulf Hansson
Wolfgang
On 2/24/19 5:27 AM, Wolfgang Grandegger wrote:
> Hello Dan,
>
> Am 22.02.19 um 18:05 schrieb Dan Murphy:
>> Wolfgang
>>
>> On 2/22/19 6:50 AM, Dan Murphy wrote:
>>> Wolfgang
>>>
>>> On 2/22/19 3:38 AM, Wolfgang Grandegger wrote:
Hello Dan,
what kernel version is that
Some real and "potential" functionalities have been shrunk in September-2018
on transition from single-big file to the current split driver onto several
files.
Regarding the MVPP2_DEFAULT_RXQ
Seems the current variant is flexible, permitting easy customize the
configuration according to
On 28 February 2019 13:40, Axel Lin wrote:
> Subject: [PATCH 09/11] regulator: pv88080: Convert to use
> regulator_set/get_current_limit_regmap
>
> Use regulator_set/get_current_limit_regmap helpers to save some code.
[...]
Hi Axel,
Looks good to me. Thanks again.
Acked-by: Steve Twiss
On Thu, 28 Feb 2019 15:12:15 +
"liujian (CE)" wrote:
> > -Original Message-
> > From: Tokunori Ikegami [mailto:ikegam...@gmail.com]
> > Sent: Thursday, February 28, 2019 10:26 PM
> > To: liujian (CE) ; dw...@infradead.org;
> > computersforpe...@gmail.com; bbrezil...@kernel.org;
> >
On 2/28/19 7:39 AM, Halil Pasic wrote:
On Thu, 28 Feb 2019 10:42:23 +0100
Christian Borntraeger wrote:
On 27.02.2019 19:00, Tony Krowiak wrote:
On 2/27/19 3:09 AM, Pierre Morel wrote:
On 26/02/2019 16:47, Tony Krowiak wrote:
On 2/26/19 6:47 AM, Pierre Morel wrote:
On 25/02/2019 19:36,
On Tue, Feb 26, 2019 at 2:46 PM Dave Hansen wrote:
>
> On 2/25/19 10:20 PM, Len Brown wrote:
> > -/* leaf 0xb sub-leaf types */
> > +/* extended topology sub-leaf types */
> > #define INVALID_TYPE 0
> > #define SMT_TYPE 1
> > #define CORE_TYPE2
> > +#define DIE_TYPE 5
>
> Looking
High latency ping. These still apply as-is.
On Fri, Dec 21, 2018 at 01:36:55PM -0800, Sean Christopherson wrote:
> Rework the messages printed for #PF oopses to display more detailed
> information about the fault in human readable form and to avoid
> conflicting messages and/or statements that
Hello,
This patchset adds MMC controller support for HI3670 SoC. Since HI3670
SoC is architecturally same as the HI3660 SoC, HI3660 DWMMC driver is
reused here with DT compatible fallback approach. Also, SD and WiFi
supports are added for the HiKey970 board.
Wei:
Please apply this patchset
Add MMC controller support for HiSilicon HI3670 SoC reusing the HI3660
Designware MMC driver. There are 2 DWMMC controllers present in this SoC:
1. DWMMC1 is used for SD card (SD)
2. DWMMC2 is used for WiFi (SDIO)
Signed-off-by: Manivannan Sadhasivam
---
HI3670 SoC is architecturally same as the HI3660 SoC. Hence, the same
K3 specific designware driver is reused for HI3670 SoC and the binding
is documented with fallback approach for compatible property.
Signed-off-by: Manivannan Sadhasivam
---
On 2/28/19 8:44 AM, Christian Borntraeger wrote:
On 28.02.2019 14:23, Pierre Morel wrote:
On 28/02/2019 10:42, Christian Borntraeger wrote:
On 27.02.2019 19:00, Tony Krowiak wrote:
On 2/27/19 3:09 AM, Pierre Morel wrote:
On 26/02/2019 16:47, Tony Krowiak wrote:
On 2/26/19 6:47 AM,
On Thu, Feb 28, 2019 at 10:37:41AM -0500, Joel Fernandes wrote:
> In any case, it is not practical to provide headers for every kernel version
> on
> the system image and maintain them, it will take up too much space and has to
> be periodically packaged. Not to mention that there will be kernel
Add SD and WiFi support for HiKey970 board based on HI3670 SoC. Due to
the absence of the PMIC driver, fixed regulators are sourced to make the
driver working.
Signed-off-by: Manivannan Sadhasivam
---
.../boot/dts/hisilicon/hi3670-hikey970.dts| 75
On Thu, Feb 28, 2019 at 04:22:04PM +0100, Dmitry Vyukov wrote:
> On Thu, Feb 28, 2019 at 4:05 PM Peter Zijlstra wrote:
> >
> > Because __asan_{load,store}{N,1,2,4,8,16}_noabort() get called from
> > UACCESS context, and kasan_report() is most definitely _NOT_ safe to
> > be called from there,
On 28 February 2019 13:40, Axel Lin wrote:
Hi Axel,
> Subject: [PATCH 10/11] regulator: pv88090: Convert to use
> regulator_set/get_current_limit_regmap
>
> Use regulator_set/get_current_limit_regmap helpers to save some code.
[...]
> @@ -193,8 +155,8 @@ static const struct regulator_ops
Yan,
On Thu, Feb 28, 2019 at 03:40:50PM +, Yan Markman wrote:
>
> Regarding the MVPP2_DEFAULT_RXQ
> Seems the current variant is flexible, permitting easy customize the
> configuration according to customer's needs.
>
> Regarding the Queue in probe():
> Looking into old code there where no2
Thanks Andy for the comments. Please see the responses below.
I'll also post the v10 patch after this email.
Regards,
Liming
> -Original Message-
> From: Andy Shevchenko
> Sent: Wednesday, February 13, 2019 1:11 PM
> To: Liming Sun
> Cc: David Woods ; Andy Shevchenko ;
> Darren Hart ;
> -Original Message-
> From: Andrew Lunn
> Sent: giovedì 28 febbraio 2019 16:33
> To: Flavio Suligoi
> Cc: Jeff Kirsher ; David S . Miller
> ; intel-wired-...@lists.osuosl.org;
> net...@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v3] net: e1000e: add MAC address
This commit adds the TmFifo platform driver for Mellanox BlueField
Soc. TmFifo is a shared FIFO which enables external host machine
to exchange data with the SoC via USB or PCIe. The driver is based
on virtio framework and has console and network access enabled.
Reviewed-by: Vadim Pasternak
On Thu, Feb 28, 2019 at 4:46 PM Peter Zijlstra wrote:
>
> On Thu, Feb 28, 2019 at 04:22:04PM +0100, Dmitry Vyukov wrote:
> > On Thu, Feb 28, 2019 at 4:05 PM Peter Zijlstra wrote:
> > >
> > > Because __asan_{load,store}{N,1,2,4,8,16}_noabort() get called from
> > > UACCESS context, and
On Thu, Feb 28, 2019 at 03:22:24PM +, Måns Rullgård wrote:
> Greg Kroah-Hartman writes:
>
> > On Thu, Feb 28, 2019 at 02:33:44PM +, Mans Rullgard wrote:
> >> Add a boolean property indicating that a device is hardwired to the
> >> upstream port. Although hubs can provide this
On Tue, Feb 26, 2019 at 11:31:11AM -0800, Jim Mattson wrote:
> On Mon, Feb 25, 2019 at 10:32 PM Yang Weijiang
> wrote:
> >
> > CET - Control-flow Enforcement Technology, it's used to
> > protect against return/jump oriented programming (ROP)
> > attacks. It provides the following capabilities to
OK-OK. The " It does fix PPv2.1 support, which was broken" is great reason!
-Original Message-
From: Antoine Tenart
Sent: Thursday, February 28, 2019 5:51 PM
To: Yan Markman
Cc: Antoine Tenart ; da...@davemloft.net;
li...@armlinux.org.uk; net...@vger.kernel.org;
On Tue, Feb 26, 2019 at 8:54 AM Peter Zijlstra wrote:
> > > It would've been nice to have the CPUID instruction 1F leaf reference
> > > 3B-3.9 in the SDM, and maybe mention this here too.
> >
> > I didn't mention SDM sections because they change -- leaving stale
> > pointers in our commit
On Mon, Feb 25, 2019 at 09:27:11PM +0800, Yang Weijiang wrote:
> Guest CET SHSTK and IBT capability are reported via
> CPUID.(EAX=7, ECX=0):ECX[bit 7] and EDX[bit 20] respectively.
> Guest user mode and supervisor mode xsaves component size
> is reported via CPUID.(EAX=0xD, ECX=1):ECX[bit 11] and
On Thu, Feb 28, 2019 at 7:45 AM Greg KH wrote:
>
> On Thu, Feb 28, 2019 at 10:37:41AM -0500, Joel Fernandes wrote:
> > In any case, it is not practical to provide headers for every kernel
> > version on
> > the system image and maintain them, it will take up too much space and has
> > to
> > be
On 2/28/19 6:52 PM, Dmitry Vyukov wrote:
> On Thu, Feb 28, 2019 at 4:46 PM Peter Zijlstra wrote:
>>
>> On Thu, Feb 28, 2019 at 04:22:04PM +0100, Dmitry Vyukov wrote:
>>> On Thu, Feb 28, 2019 at 4:05 PM Peter Zijlstra wrote:
Because __asan_{load,store}{N,1,2,4,8,16}_noabort() get
Hi,
Here is the v5 series of probe-event to support user-space access.
This version I simplified probe_user_read (Thanks PeterZ!) and move
open-coded non-pagefault strnlen_user code to mm/maccess.c.
Changes in v5:
- [3/6]: Simplify probe_user_read() and add strnlen_unsafe_user()
- [4/6]: Use
On Thu, Feb 28, 2019 at 4:46 PM Peter Zijlstra wrote:
>
> On Thu, Feb 28, 2019 at 04:22:04PM +0100, Dmitry Vyukov wrote:
> > On Thu, Feb 28, 2019 at 4:05 PM Peter Zijlstra wrote:
> > >
> > > Because __asan_{load,store}{N,1,2,4,8,16}_noabort() get called from
> > > UACCESS context, and
Use user_access_ok() instead of access_ok() in user_access_begin()
to validate the access context is user. This also allow us to
use (generic) strncpy_from_user() and strnlen_user() in atomic
state with setting USER_DS and disable pagefaults.
Signed-off-by: Masami Hiramatsu
---
From: Peter Zijlstra
Add user_access_ok() macro which ensures current context
is user context, or explicitly do set_fs(USER_DS).
This function is very much like access_ok(), except it (may)
have different context validation. In general we must be
very careful when using this.
Signed-off-by:
Add probe_user_read(), strncpy_from_unsafe_user() and
strnlen_unsafe_user() which allows caller to access user-space
in IRQ context.
Current probe_kernel_read() and strncpy_from_unsafe() are
not available for user-space memory, because it sets
KERNEL_DS while accessing data. On some arch, user
On Mon, Feb 25, 2019 at 09:27:10PM +0800, Yang Weijiang wrote:
> Guest queries CET SHSTK and IBT support by CPUID.(EAX=0x7,ECX=0),
> in return, ECX[bit 7] corresponds to SHSTK feature, and EDX[bit 20]
> corresponds to IBT feature.
> CR4.CET[bit 23] is CET master enable bit, it controls CET feature
Add "ustring" type for fetching user-space string from kprobe event.
User can specify ustring type at uprobe event, and it is same as
"string" for uprobe.
Note that probe-event provides this option but it doesn't choose the
correct type automatically since we have not way to decide the address
is
Hi Joel,
On 2/28/19 3:47 PM, Joel Fernandes wrote:
On Thu, Feb 28, 2019 at 01:53:43PM +, Qais Yousef wrote:
Hi Joel
On 02/27/19 14:37, Joel Fernandes (Google) wrote:
[...]
Ah good catch, I made this change for "file_list=${@:2}" in my tree but
forgot to push it. Below is the updated
Support user-space dereference syntax for probe event arguments
to dereference the data-structure or array in user-space.
The syntax is just adding 'u' before an offset value.
+|-u()
e.g. +u8(%ax), +u0(+0(%si))
For example, if you probe do_sched_setscheduler(pid, policy,
param) and record
Add a user-memory access syntax testcase which checks
new user-memory access syntax and ustring type.
Signed-off-by: Masami Hiramatsu
---
.../ftrace/test.d/kprobe/kprobe_args_user.tc | 31
1 file changed, 31 insertions(+)
create mode 100644
On Thu, 28 Feb 2019 16:45:13 +0100
Greg KH wrote:
> On Thu, Feb 28, 2019 at 10:37:41AM -0500, Joel Fernandes wrote:
> > In any case, it is not practical to provide headers for every kernel
> > version on
> > the system image and maintain them, it will take up too much space and has
> > to
> >
On Thu, Feb 28, 2019 at 09:07:19PM +0530, Ravi Bangoria wrote:
> perf c2c report fails if system has empty numa node(0 cpus):
>
> $ lscpu
> NUMA node0 CPU(s):
> NUMA node1 CPU(s): 0-4
>
> $ sudo ./perf c2c report
> node/cpu topology bugFailed setup nodes
>
> Fix this.
>
>
On Wed, Feb 20, 2019 at 10:03:55PM +0530, Srinath Mannam wrote:
> In the present driver outbound window configuration is done to map above
> 32-bit address I/O regions with corresponding PCI memory range given in
> ranges DT property.
>
> This patch add outbound window configuration to map below
On Tue, 12 Feb 2019 16:14:08 +0100, Neil Armstrong wrote:
> Adds the specific compatible string for the DWC2 IP found in the
> Amlogic G12A SoC Family.
>
> Signed-off-by: Neil Armstrong
> ---
> Documentation/devicetree/bindings/usb/dwc2.txt | 1 +
> 1 file changed, 1 insertion(+)
>
On Mon, Feb 25, 2019 at 09:27:14PM +0800, Yang Weijiang wrote:
> "Load Guest CET state" bit controls whether guest CET states
> will be loaded at Guest entry. Before doing that, KVM needs
> to check if CPU CET feature is available.
>
> Signed-off-by: Zhang Yi Z
> Signed-off-by: Yang Weijiang
>
On 02/28/2019 01:53 PM, H.J. Lu wrote:
> On Thu, Feb 28, 2019 at 3:27 AM David Woodhouse wrote:
>> On Thu, 2019-02-28 at 03:12 -0800, tip-bot for Daniel Borkmann wrote:
>>> Commit-ID: ce02ef06fcf7a399a6276adb83f37373d10cbbe1
>>> Gitweb:
>>>
On Thu, 28 Feb 2019 09:11:37 +
Pavel Tikhomirov wrote:
> ping, looks like the patch was lost
>
> On 8/24/18 3:48 AM, Steven Rostedt wrote:
> > On Thu, 23 Aug 2018 13:25:34 +0300
> > Pavel Tikhomirov wrote:
> >
> >> Then tracing syscall exit event it is extremely useful to filter exit
>
On Thu, 28 Feb 2019 16:00:55 +0900
Masami Hiramatsu wrote:
> >
> > "+u0(%si):string will read a string from the address in the register
> > %si that is expected to be in user-space. 'ustring' is a shortcut way
> > off performing the same task. That is, +0(%si):ustring is equivalent
> > to
On Thu, Feb 28, 2019 at 05:12:31PM +0100, Jiri Olsa wrote:
> On Thu, Feb 28, 2019 at 09:07:19PM +0530, Ravi Bangoria wrote:
> > perf c2c report fails if system has empty numa node(0 cpus):
> >
> > $ lscpu
> > NUMA node0 CPU(s):
> > NUMA node1 CPU(s): 0-4
> >
> > $ sudo ./perf c2c
On 02/28/19 17:04, Dietmar Eggemann wrote:
> Hi Joel,
>
> On 2/28/19 3:47 PM, Joel Fernandes wrote:
> > On Thu, Feb 28, 2019 at 01:53:43PM +, Qais Yousef wrote:
> > > Hi Joel
> > >
> > > On 02/27/19 14:37, Joel Fernandes (Google) wrote:
>
> [...]
>
> > Ah good catch, I made this change for
On Mon, Feb 25, 2019 at 09:27:15PM +0800, Yang Weijiang wrote:
> For Guest XSS, right now, only bit 11(user states) and bit 12
> (supervisor states) are supported, if other bits are being set,
> need to modify KVM_SUPPORTED_XSS macro to have support.
The changelog should describe what the change
On Thu, Feb 28, 2019 at 8:18 AM Daniel Borkmann wrote:
>
> On 02/28/2019 01:53 PM, H.J. Lu wrote:
> > On Thu, Feb 28, 2019 at 3:27 AM David Woodhouse wrote:
> >> On Thu, 2019-02-28 at 03:12 -0800, tip-bot for Daniel Borkmann wrote:
> >>> Commit-ID: ce02ef06fcf7a399a6276adb83f37373d10cbbe1
> >>>
On Tue, Feb 12, 2019 at 04:14:09PM +0100, Neil Armstrong wrote:
> Adds the bindings for the Amlogic G12A USB Glue HW.
>
> The Amlogic G12A SoC Family embeds 2 USB Controllers :
> - a DWC3 IP configured as Host for USB2 and USB3
> - a DWC2 IP configured as Peripheral USB2 Only
>
> A glue connects
[ Resend #2: Sorry about the spam, I mixed up the header fields in
git-send-email and I don't know who did and didn't receive the
garbled previous attempt.
Resend #1: Rebased on top of the latest mmots. ]
The memcg LRU stats usage is currently a bit messy. Memcg has private
per-zone
The memcg code currently maintains private per-zone breakdowns of the
LRU counters. This is necessary for reclaim decisions which are still
zone-based, but there are a variety of users of these counters that
only want the aggregate per-lruvec or per-memcg LRU counts, and they
need to painfully sum
mem_cgroup_node_nr_lru_pages() is just a convenience wrapper around
lruvec_page_state() that takes bitmasks of lru indexes and aggregates
the counts for those.
Replace callsites where the bitmask is simple enough with direct
lruvec_page_state() calls.
This removes the last extern user of
Only memcg_numa_stat_show() uses those wrappers and the lru bitmasks,
group them together.
Signed-off-by: Johannes Weiner
---
include/linux/mmzone.h | 5
mm/memcontrol.c| 67 +++---
2 files changed, 36 insertions(+), 36 deletions(-)
diff --git
Instead of adding up the zone counters, use lruvec_page_state() to get
the node state directly. This is a bit cheaper and more stream-lined.
Signed-off-by: Johannes Weiner
---
include/linux/memcontrol.h | 18 --
mm/memcontrol.c| 2 +-
mm/vmscan.c| 2
Instead of adding up the node counters, use memcg_page_state() to get
the memcg state directly. This is a bit cheaper and more stream-lined.
Signed-off-by: Johannes Weiner
---
mm/memcontrol.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/mm/memcontrol.c
mem_cgroup_nr_lru_pages() is just a convenience wrapper around
memcg_page_state() that takes bitmasks of lru indexes and aggregates
the counts for those.
Replace callsites where the bitmask is simple enough with direct
memcg_page_state() call(s).
Signed-off-by: Johannes Weiner
---
On Mon, Feb 25, 2019 at 09:27:16PM +0800, Yang Weijiang wrote:
> The Guest MSRs are stored in fpu storage area, they are
> operated by XSAVES/XRSTORS, so use kvm_load_guest_fpu
> to restore them is a convenient way to let KVM access
> them. After finish operation, need to restore Host MSR
>
On Thu, Feb 28, 2019 at 1:57 PM Thomas Gleixner wrote:
> On Thu, 28 Feb 2019, Jann Horn wrote:
> > +Josh for unwinding, +x86 folks
> > On Wed, Feb 27, 2019 at 11:43 PM Andrew Morton
> > wrote:
> > > On Thu, 21 Feb 2019 06:52:04 -0800 syzbot
> > > wrote:
> > >
> > > > Hello,
> > > >
> > > >
> Hi Andrew,
>
> we produce a lot of boards and we have to change the MAC address,
> from u-boot, for every board. So I must save in the u-boot
> environment (SPI NOR flash) the MAC address for every board.
Hi Flavio
u-boot should be able to write the MAC address in the correct part of
device
Hi Lorenzo,
Thanks for the review.. Please see my comments below in line..
Regards,
Srinath.
On Thu, Feb 28, 2019 at 9:43 PM Lorenzo Pieralisi
wrote:
>
> On Wed, Feb 20, 2019 at 10:03:55PM +0530, Srinath Mannam wrote:
> > In the present driver outbound window configuration is done to map above
701 - 800 of 1382 matches
Mail list logo
