Resend this mail.
On 2019-01-18 08:17, Kees Cook wrote:
> On Mon, Jan 7, 2019 at 4:01 AM liaoweixiong
> wrote:
>>
>> To enable pmsg, just set pmsg_size when block device register blkzone.
>
> At first pass, this looks like a reasonable extension of blkzone. Is
> it possible to add console, ftrac
On 2019-01-18 08:17, Kees Cook wrote:
> On Mon, Jan 7, 2019 at 4:01 AM liaoweixiong
> wrote:
>>
>> To enable pmsg, just set pmsg_size when block device register blkzone.
>
> At first pass, this looks like a reasonable extension of blkzone. Is
> it possible to add console, ftrace, etc, too?
>
I
RSDP is needed by both KASLR, so parse it early and fill it in
boot_params before KASLR code.
RSDP is needed by lots of other code, it would be easier to have it
always built-in instead of a long "depends on" line in Kconfig.
Signed-off-by: Chao Fan
---
arch/x86/boot/compressed/Makefile | 2 ++
Memory information in SRAT table is necessary to fix the conflict
between KASLR and memory-hotremove. So RSDP and SRAT should be parsed.
When booting form KEXEC/EFI/BIOS, the methods to compute RSDP
are different. When booting from BIOS, there is no variable who can
point to RSDP directly, so scan
***Background:
People reported that KASLR may randomly choose some positions
which are located in movable memory regions. This will make the
movable memory chosen by KASLR can't be removed.
***Solutions:
Get the information of memory hot-remove, then KASLR knows the
right regions. Information abou
KASLR may randomly choose some positions which are located in movable
memory regions. It will break memory hotplug feature and make the
movable memory chosen by KASLR can't be removed.
The solution is to limit KASLR to choose memory regions in immovable
node according to SRAT tables.
When CONFIG_E
Memory information in SRAT is necessary to fix the conflict between
KASLR and memory-hotremove. So RSDP and SRAT should be parsed.
When booting form KEXEC/EFI/BIOS, the methods to compute RSDP
are different. When booting from EFI, EFI table points to RSDP.
So parse the EFI table and find the RSDP.
Copy kstrtoull() and necessary functions from lib/kstrtox.c to
boot/string.c so that code in boot/ can use kstrtoull() and the old
simple_strtoull() can be replaced.
In boot/string.c, using div_u64() from math64.h directly will cause the
dividend handled as 64-bit value and bring ld error. The sol
SRAT should be parsed by RSDP to fix the conflict between KASLR and
memory-hotremove, then filter the immovable memory regions and
accoring to the memory information, KASLR can avoid to extract kernel
to movable memory regions.
Signed-off-by: Chao Fan
---
arch/x86/boot/compressed/acpi.c | 122 +
KASLR may randomly choose some positions which are located in movable
memory regions. This will make the movable memory chosen by KASLR
can't be removed.
Memory information in SRAT is necessary to fix the conflict between
KASLR and memory-hotremove.
ACPI SRAT (System/Static Resource Affinity Tabl
On Wed 23-01-19 11:28:14, Greg KH wrote:
> When an error happens, debugfs should return an error pointer value, not
> NULL. This will prevent the totally theoretical error where a debugfs
> call fails due to lack of memory, returning NULL, and that dentry value
> is then passed to another debugfs
This attempts to duplicate the proposed gcc option -finit-local-vars[1]
in an effort to implement the "always initialize local variables" kernel
development goal[2].
Enabling CONFIG_GCC_PLUGIN_STACKINIT should stop all "uninitialized
stack variable" flaws as long as they don't depend on being zero
On Thu, 2019-01-10 at 16:05 -0800, Joe Perches wrote:
> Using SPDX commenting style // or /* is specified for
> various file types in Documentation/process/license-rules.rst
> so add an appropriate test for .[chsS] files because many
> proposed file additions and patches do not use the correct styl
On 23.01.2019 14:02, Michal Hocko wrote:
> On Wed 23-01-19 13:28:03, Kirill Tkhai wrote:
>> On 22.01.2019 23:09, Yang Shi wrote:
>>> In current implementation, both kswapd and direct reclaim has to iterate
>>> all mem cgroups. It is not a problem before offline mem cgroups could
>>> be iterated.
This adds a new plugin "stackinit" that attempts to perform unconditional
initialization of all stack variables[1]. It has wider effects than
GCC_PLUGIN_STRUCTLEAK_BYREF_ALL=y since BYREF_ALL does not consider
non-structures. A notable weakness is that padding bytes in many cases
remain uninitializ
On Sat, 2019-01-12 at 12:45 -0800, Joe Perches wrote:
> Many new generic allocation functions like the
> kvmalloc family have been added recently to the kernel.
ping?
Adds test for stack initialization coverage. We have several build options
that control the level of stack variable initialization. This test lets us
visualize which options cover which cases, and provide tests for options
that are currently not available (padding initialization).
All options pass
Variables declared in a switch statement before any case statements
cannot be initialized, so move all instances out of the switches.
After this, future always-initialized stack variables will work
and not throw warnings like this:
fs/fcntl.c: In function ‘send_sigio_to_task’:
fs/fcntl.c:738:13: w
Hi Andrew,
Thanks for taking a look at this.
> -Original Message-
> From: Andrew Murray [mailto:andrew.mur...@arm.com]
> Sent: 22 January 2019 16:24
> To: Shameerali Kolothum Thodi
> Cc: lorenzo.pieral...@arm.com; robin.mur...@arm.com;
> mark.rutl...@arm.com; vkil...@codeaurora.org; neil
On Wed 23-01-19 13:28:03, Kirill Tkhai wrote:
> On 22.01.2019 23:09, Yang Shi wrote:
> > In current implementation, both kswapd and direct reclaim has to iterate
> > all mem cgroups. It is not a problem before offline mem cgroups could
> > be iterated. But, currently with iterating offline mem cg
The document, at Documentation/admin-guide/pstore-block.rst,
tells user how to use pstore_blk and the attentions about panic
read/write
Signed-off-by: liaoweixiong
---
Documentation/admin-guide/pstore-block.rst | 227 +
MAINTAINERS| 1
blkoops is a sample for pstore/blk. It can only record oops, excluding
panics as no read/write apis for panic registered. It support settings
on Kconfg/device tree/module parameters. It can record oops log even
power failure if "PSTORE_BLKOOPS_PART_PATH" on Kconfig or
"partition-path" on dts or "pa
Why should we need pstore_block?
1. Most embedded intelligent equipment have no persistent ram, which
increases costs. We perfer to cheaper solutions, like block devices.
In fast, there is already a sample for block device logger in driver
MTD (drivers/mtd/mtdoops.c).
2. Do not any equipment have b
pstore_blk is similar to pstore_ram, but dump log to block devices
rather than persistent ram.
Why should we need pstore_blk?
1. Most embedded intelligent equipment have no persistent ram, which
increases costs. We perfer to cheaper solutions, like block devices.
In fact, there is already a sample
To enable pmsg, just set pmsg_size when block device register blkzone.
Signed-off-by: liaoweixiong
---
fs/pstore/blkoops.c| 11 ++
fs/pstore/blkzone.c| 254 +
include/linux/pstore_blk.h | 1 +
3 files changed, 244 insertions(+), 22 d
On Wed, Jan 23, 2019 at 11:54:58AM +0100, Christian Brauner wrote:
> On Thu, Jan 17, 2019 at 12:48:54PM +0100, Christian Brauner wrote:
> > This adds the promised selftest for binderfs. It will verify the following
> > things:
> > - binderfs mounting works
> > - binder device allocation works
> > -
On Wed, Jan 23, 2019 at 12:45:30PM +0530, al...@codeaurora.org wrote:
> On 2019-01-23 01:59, Mark Brown wrote:
> > Still not seeing anything except this patch here in my inbox - like I
> > said what's the story with dependencies?
> I've added linux-spi mailing list to all the patches sent as part
Good day!!! I am Miss Julian Mene, 24 year old, an orphan from Democratic
Republic of Congo (DRC), but presently in Benin Republic. I have something very
urgent and important to discuss with you. I assure you that you will not regret
anything. Please send your reply to my personal email: me...@r
On Thu, Jan 17, 2019 at 12:48:54PM +0100, Christian Brauner wrote:
> This adds the promised selftest for binderfs. It will verify the following
> things:
> - binderfs mounting works
> - binder device allocation works
> - performing a binder ioctl() request through a binderfs device works
> - binder
On Wed, Jan 23, 2019 at 11:53 AM Amit Kucheria wrote:
>
> On Wed, Jan 23, 2019 at 4:04 PM Viresh Kumar wrote:
> >
> > On 21-01-19, 21:10, Amit Kucheria wrote:
> > > The CPU cooling driver (cpu_cooling.c) allows the platform's cpufreq
> > > driver to register as a cooling device and cool down the
On Wed, Jan 23, 2019 at 11:44 AM Viresh Kumar wrote:
>
> On 23-01-19, 16:13, Viresh Kumar wrote:
> > On 23-01-19, 11:39, Rafael J. Wysocki wrote:
> > > On Wed, Jan 23, 2019 at 11:36 AM Viresh Kumar
> > > wrote:
> > > >
> > > > On 21-01-19, 21:10, Amit Kucheria wrote:
> > > > > @@ -151,6 +152,11
On Wed, Jan 23, 2019 at 4:04 PM Viresh Kumar wrote:
>
> On 21-01-19, 21:10, Amit Kucheria wrote:
> > The CPU cooling driver (cpu_cooling.c) allows the platform's cpufreq
> > driver to register as a cooling device and cool down the platform by
> > throttling the CPU frequency. In order to be able t
On Thu, 2019-01-17 at 14:38 -0800, Andrey Smirnov wrote:
[...]
> > To be honest, I don't like these two, I'm not convinced anymore that
> > they actually qualify as reset signals. To me it looks like this is
> > something that the PCIe glue code should handle via syscon like i.MX6.
> > Leonard, Luc
On Wed, Jan 23, 2019 at 07:47:47AM +1100, Stephen Rothwell wrote:
> Hi Christoph,
>
> In commit
>
> 702e8ed37bed ("arm64/xen: fix xen-swiotlb cache flushing")
Hi Christoph,
I'm not subscribed to any of the mailing list that the above patch was
reviewed on, so I'm replying here because it is t
Hi Andrey,
On Mon, 2019-01-21 at 18:10 -0800, Andrey Smirnov wrote:
> Add bits and pieces needed to support IP block variant found on
> i.MX8MQ SoCs.
>
> Cc: p.za...@pengutronix.de
> Cc: Fabio Estevam
> Cc: cphe...@gmail.com
> Cc: l.st...@pengutronix.de
> Cc: Leonard Crestez
> Cc: "A.s. Dong"
On Tue, Jan 15, 2019 at 10:15:06AM +, Patrick Bellasi wrote:
> @@ -858,16 +859,23 @@ static inline void
> uclamp_effective_get(struct task_struct *p, unsigned int clamp_id,
>unsigned int *clamp_value, unsigned int *bucket_id)
> {
> + struct uclamp_se *default_clamp;
>
On 22/01/2019 15:21, Catalin Marinas wrote:
> On Mon, Jan 21, 2019 at 03:33:31PM +, Julien Thierry wrote:
>> diff --git a/arch/arm64/include/asm/irqflags.h
>> b/arch/arm64/include/asm/irqflags.h
>> index 24692ed..7e82a92 100644
>> --- a/arch/arm64/include/asm/irqflags.h
>> +++ b/arch/arm64/
On 23-01-19, 16:13, Viresh Kumar wrote:
> On 23-01-19, 11:39, Rafael J. Wysocki wrote:
> > On Wed, Jan 23, 2019 at 11:36 AM Viresh Kumar
> > wrote:
> > >
> > > On 21-01-19, 21:10, Amit Kucheria wrote:
> > > > @@ -151,6 +152,11 @@ struct cpufreq_policy {
> > > >
> > > > /* For cpufreq driver
On 23-01-19, 11:39, Rafael J. Wysocki wrote:
> On Wed, Jan 23, 2019 at 11:36 AM Viresh Kumar wrote:
> >
> > On 21-01-19, 21:10, Amit Kucheria wrote:
> > > @@ -151,6 +152,11 @@ struct cpufreq_policy {
> > >
> > > /* For cpufreq driver's internal use */
> > > void*dri
> When calling debugfs functions, there is no need to ever check the
> return value. The function can work or not, but the code logic should
> never do something different based on this.
>
> Cc: Igor Mitsyanko
> Cc: Avinash Patil
> Cc: Sergey Matyukevich
> Cc: Kalle Valo
> Cc: linux-wirel...@
Bartosz Golaszewski writes:
> pon., 14 sty 2019 o 13:20 Sekhar Nori napisał(a):
>>
>> Hi Bartosz,
>>
>> On 11/01/19 10:51 PM, Bartosz Golaszewski wrote:
>> > From: Bartosz Golaszewski
>> >
>> > Currently the clocksource and clockevent support for davinci platforms
>> > lives in mach-davinci. It
Hi folks,
Fedora has received a number of reports of e1000e-driven ethernet ports
negotiating 10Mbps links if the cable is disconnected and reconnected
after boot on a number of laptops, including the Lenovo T480s[0].
Kamil git-bisected the issue to commit cc365dcf0e56 ("mei: me: allow
runtime pm
Hi Alex,
On Wed, 2019-01-23 at 18:43 +0900, Alexandre Courbot wrote:
> On Tue, Jan 22, 2019 at 7:10 PM Paul Kocialkowski
> wrote:
> > Hi,
> >
> > On Tue, 2019-01-22 at 17:19 +0900, Tomasz Figa wrote:
> > > Hi Paul,
> > >
> > > On Fri, Dec 7, 2018 at 5:30 PM Paul Kocialkowski
> > > wrote:
> > >
Thank you Simon.
Fab
> From: Simon Horman
> Sent: 23 January 2019 10:39
> Subject: Re: linux-next: Fixes tag needs some work in the renesas tree
>
> [CC linux-renesas-soc]
>
> On Wed, Jan 23, 2019 at 08:55:21AM +, Fabrizio Castro wrote:
> > > From: Stephen Rothwell
> > > Sent: 22 January 20
This correct maximum hardware load constant in per SoC resources
for sdm845 aka Venus v4.
Reviewed-by: Alexandre Courbot
Tested-by: Alexandre Courbot
Signed-off-by: Stanimir Varbanov
---
drivers/media/platform/qcom/venus/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Hello,
Changes in v2:
* in 1/4 make 'mapped' const - Alex
* fixed typos in 2/4 and 4/4 - Alex
* added Reviewed-by and Tested-by tags
regards,
Stan
Stanimir Varbanov (4):
venus: firmware: check fw size against DT memory region size
venus: core: correct maximum hardware load for sdm845
ve
By historical reasons we defined firmware memory size to be 6MB even
that the firmware size for all supported Venus versions is 5MBs. Correct
that by compare the required firmware size returned from mdt loader and
the one provided by DT reserved memory region. We proceed further if the
required fir
The zero timestamp is really valid so fix that mistake by
dropping the code which checks for zero timestamp.
Reviewed-by: Alexandre Courbot
Tested-by: Alexandre Courbot
Signed-off-by: Stanimir Varbanov
---
drivers/media/platform/qcom/venus/helpers.c | 3 ---
1 file changed, 3 deletions(-)
dif
This corrects clock frequency table rates to be in sync
with video clock controller frequency table.
Reviewed-by: Alexandre Courbot
Tested-by: Alexandre Courbot
Signed-off-by: Stanimir Varbanov
---
drivers/media/platform/qcom/venus/core.c | 10 ++
1 file changed, 6 insertions(+), 4 del
On Tue, Jan 22, 2019 at 07:46:46AM +, Corentin Labbe wrote:
> This patch enable HDMI output on sun8i-h3-nanopi-m1-plus.
>
> Signed-off-by: Corentin Labbe
The prefix must be "ARM: dts:"
I've fixed it and applied, thanks!
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineerin
On Wed, Jan 23, 2019 at 11:36 AM Viresh Kumar wrote:
>
> On 21-01-19, 21:10, Amit Kucheria wrote:
> > @@ -151,6 +152,11 @@ struct cpufreq_policy {
> >
> > /* For cpufreq driver's internal use */
> > void*driver_data;
> > +
> > +#ifdef CONFIG_CPU_THERMAL
> > + /*
[CC linux-renesas-soc]
On Wed, Jan 23, 2019 at 08:55:21AM +, Fabrizio Castro wrote:
> > From: Stephen Rothwell
> > Sent: 22 January 2019 20:56
> > To: Simon Horman
> > Subject: linux-next: Fixes tag needs some work in the renesas tree
> >
> > Hi all,
> >
> > In commit
> >
> > 8d6e2bbaeceb
On 21-01-19, 21:10, Amit Kucheria wrote:
> @@ -151,6 +152,11 @@ struct cpufreq_policy {
>
> /* For cpufreq driver's internal use */
> void*driver_data;
> +
> +#ifdef CONFIG_CPU_THERMAL
> + /* Pointer to the cooling device if used for thermal mitigation */
> +
samples/livepatch//livepatch-shadow-fix1.c:97:30-36: ERROR: application of
sizeof to pointer
Patch was compile tested with: x86_64_defconfig + FTRACE=y,
FUNCTION_TRACER=y, SAMPLES=y, LIVEPATCH=y SAMPLE_LIVEPATCH=m
Patch is against 5.0-rc3 (localversion-next is next-20190123)
samples/livepatch
On 21-01-19, 21:10, Amit Kucheria wrote:
> The CPU cooling driver (cpu_cooling.c) allows the platform's cpufreq
> driver to register as a cooling device and cool down the platform by
> throttling the CPU frequency. In order to be able to auto-register a
> cpufreq driver as a cooling device from the
On 22.01.19 16:44, Oscar Salvador wrote:
> This is the same sort of error we saw in [1].
>
> Gigantic hugepages crosses several memblocks, so it can be
> that the page we get in scan_movable_pages() is a page-tail
> belonging to a 1G-hugepage.
> If that happens, page_hstate()->size_to_hstate() wil
On Wed, Jan 23, 2019 at 09:20:05AM +0100, Ulf Hansson wrote:
> On Wed, 23 Jan 2019 at 08:59, Greg Kroah-Hartman
> wrote:
> >
> > On Wed, Jan 23, 2019 at 08:44:36AM +0100, Ulf Hansson wrote:
> > > On Tue, 22 Jan 2019 at 16:23, Greg Kroah-Hartman
> > > wrote:
> > > >
> > > > When calling debugfs fu
On 23/01/19 2:19 PM, YueHaibing wrote:
> There is no need to have the 'gpio_unbanked' variable static since
> new value always be assigned before use it.
Acked-by: Keerthy
>
> Signed-off-by: YueHaibing
> ---
> drivers/gpio/gpio-davinci.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletion
On Wed, Jan 23, 2019 at 11:29:30AM +0100, Greg Kroah-Hartman wrote:
> On Wed, Jan 23, 2019 at 11:28:14AM +0100, Greg Kroah-Hartman wrote:
> > When an error happens, debugfs should return an error pointer value, not
> > NULL. This will prevent the totally theoretical error where a debugfs
> > call
From:MR.JAMES KABORE.
Bill and Exchange Manager
Micro Finance Bank Plc
Burkina Faso
Dear Friend,
I know that this mail will come to you as a surprise. I am MR.JAMES
KABORE. and I am the bill and Exchange manager in a Bank here in my
country .I Hope that you will not expose or betray this trust a
On Wed, Jan 23, 2019 at 11:28:14AM +0100, Greg Kroah-Hartman wrote:
> When an error happens, debugfs should return an error pointer value, not
> NULL. This will prevent the totally theoretical error where a debugfs
> call fails due to lack of memory, returning NULL, and that dentry value
> is then
When an error happens, debugfs should return an error pointer value, not
NULL. This will prevent the totally theoretical error where a debugfs
call fails due to lack of memory, returning NULL, and that dentry value
is then passed to another debugfs call, which would end up succeeding,
creating a f
On Tue, Jan 15, 2019 at 10:15:06AM +, Patrick Bellasi wrote:
> - util = (type == ENERGY_UTIL)
> - ? util_cfs
> - : uclamp_util(rq, util_cfs);
> - util += cpu_util_rt(rq);
> + util = cpu_util_rt(rq);
> + if (type == FREQUENCY_UTIL) {
> + util +
On 22.01.2019 23:09, Yang Shi wrote:
> In current implementation, both kswapd and direct reclaim has to iterate
> all mem cgroups. It is not a problem before offline mem cgroups could
> be iterated. But, currently with iterating offline mem cgroups, it
> could be very time consuming. In our work
debugfs_rename() needs to check that the dentries passed into it really
are valid, as sometimes they are not (i.e. if the return value of
another debugfs call is passed into this one.) So fix this up by
properly checking if the two parent directories are errors (they are
allowed to be NULL), and i
On Wed 23-01-19 11:18:42, Oscar Salvador wrote:
> On Wed, Jan 23, 2019 at 10:47:17AM +0100, Michal Hocko wrote:
> > So this should be probably folded into the above patch as it is
> > incomplete unless I am missing something.
>
> Well, they are triggered from different paths.
> The former error wa
update SPDX License Identifier from GPL-2.0+ to GPL-2.0
and drop some GPL text.
Signed-off-by: Sandy Huang
---
drivers/gpu/drm/rockchip/rockchip_rgb.c | 11 +--
drivers/gpu/drm/rockchip/rockchip_rgb.h | 11 +--
2 files changed, 2 insertions(+), 20 deletions(-)
diff --git a/drive
On Tue, Jan 22, 2019 at 02:55:22PM +, Mark Rutland wrote:
> On Tue, Jan 22, 2019 at 05:44:02AM +, Will Deacon wrote:
> > On Mon, Jan 21, 2019 at 02:21:28PM +, Catalin Marinas wrote:
> > > On Sat, Jan 19, 2019 at 11:58:27PM +, Will Deacon wrote:
> > > > On Thu, Jan 17, 2019 at 07:42:
On Wed, Jan 23, 2019 at 10:47:17AM +0100, Michal Hocko wrote:
> So this should be probably folded into the above patch as it is
> incomplete unless I am missing something.
Well, they are triggered from different paths.
The former error was triggered in:
removable_show
is_mem_section_removable
Thanks for the review,
On 22/01/2019 18:41, Mark Brown wrote:
On Thu, Jan 10, 2019 at 03:06:10PM +, Srinivas Kandagatla wrote:
This all looks good apart from a couple of small things that should be
easy to fix:
diff --git a/sound/soc/codecs/Kconfig b/sound/soc/codecs/Kconfig
index 62bdb7e
Thanks for the review,
On 22/01/2019 18:52, Mark Brown wrote:
On Thu, Jan 10, 2019 at 03:06:12PM +, Srinivas Kandagatla wrote:
+static const char * const wcd9335_ear_pa_gain_text[] = {
+ "G_6_DB", "G_4P5_DB", "G_3_DB", "G_1P5_DB",
+ "G_0_DB", "G_M2P5_DB", "UNDEFINED", "G_M12_DB
On 23.01.19 08:26, Martin Kepplinger wrote:
From: Martin Kepplinger
Add support for the Sitronix ST1633 touchscreen controller to the st1232
driver.
FYI, here's a protocol spec:
www.ampdisplay.com/documents/pdf/AM-320480B6TZQW-TC0H.pdf
Let me know if you want that link in the commit message
Hi Alex,
Thanks for the review!
On 1/23/19 8:10 AM, Alexandre Courbot wrote:
> Sorry for the delayed review! >_<
>
> On Wed, Jan 9, 2019 at 5:46 PM Stanimir Varbanov
> wrote:
>>
>> By historical reasons we defined firmware memory size to be 6MB even
>> that the firmware size for all supported V
On Wed, Jan 23, 2019 at 06:00:14PM +0800, Cao jin wrote:
> gdt64 represents the content of GDTR under x86-64, which actually needs
> 10 bytes only, ".long" & ".word" is superfluous.
>
> Signed-off-by: Cao jin
Acked-by: Kirill A. Shutemov
--
Kirill A. Shutemov
Hi Rob,
On 22/01/19 6:18 AM, Rob Herring wrote:
> On Mon, Jan 14, 2019 at 06:54:09PM +0530, Kishon Vijay Abraham I wrote:
>> Document "atu" reg-names required to get the register space for ATU in
>> Synopsys designware core version >= 4.80.
>>
>> Signed-off-by: Kishon Vijay Abraham I
>> ---
>> D
Le 12/01/2019 à 10:55, Christophe Leroy a écrit :
The purpose of this serie is to activate CONFIG_THREAD_INFO_IN_TASK which
moves the thread_info into task_struct.
Moving thread_info into task_struct has the following advantages:
- It protects thread_info from corruption in the case of stack
On Wed, Jan 23, 2019 at 12:01:23PM +0800, Cao jin wrote:
> Thanks for your info! BTW, could I know how you construct the test
> environment?
Nothing fancy. I just built different versions of binutils from git.
--
Kirill A. Shutemov
gdt64 represents the content of GDTR under x86-64, which actually needs
10 bytes only, ".long" & ".word" is superfluous.
Signed-off-by: Cao jin
---
arch/x86/boot/compressed/head_64.S | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/x86/boot/compressed/head_64.S
b/arch/x86/boot/compress
On Sun, Nov 18, 2018 at 10:34 AM Nicolas Dufresne wrote:
>
> Le samedi 17 novembre 2018 à 12:37 +0100, Hans Verkuil a écrit :
> > > > Does V4L2_CID_MIN_BUFFERS_FOR_CAPTURE make any sense for encoders?
> > >
> > > We do account for it in GStreamer (the capture/output handling is
> > > generic), but
On Sat, Nov 17, 2018 at 8:37 PM Hans Verkuil wrote:
>
> On 11/17/2018 05:18 AM, Nicolas Dufresne wrote:
> > Le lundi 12 novembre 2018 à 14:23 +0100, Hans Verkuil a écrit :
> >> On 10/22/2018 04:49 PM, Tomasz Figa wrote:
[snip]
> >>> + rely on it. The ``V4L2_BUF_FLAG_LAST`` buffer flag should
On Wed 23-01-19 04:09:42, Yang Shi wrote:
> In current implementation, both kswapd and direct reclaim has to iterate
> all mem cgroups. It is not a problem before offline mem cgroups could
> be iterated. But, currently with iterating offline mem cgroups, it
> could be very time consuming. In our
This series tries to access virtqueue metadata through kernel virtual
address instead of copy_user() friends since they had too much
overheads like checks, spec barriers or even hardware feature
toggling.
Test shows about 24% improvement on TX PPS. It should benefit other
cases as well.
Changes f
Rename the function to be more accurate since it actually tries to
prefetch vq metadata address in IOTLB. And this will be used by
following patch to prefetch metadata virtual addresses.
Signed-off-by: Jason Wang
---
drivers/vhost/net.c | 4 ++--
drivers/vhost/vhost.c | 4 ++--
drivers/vhost/v
Use one generic vhost_copy_to_user() instead of two dedicated
accessor. This will simplify the conversion to fine grain
accessors. About 2% improvement of PPS were seen during vitio-user
txonly test.
Signed-off-by: Jason Wang
---
drivers/vhost/vhost.c | 11 +--
1 file changed, 1 insertio
Signed-off-by: Jason Wang
---
drivers/vhost/vhost.c | 46 ++-
1 file changed, 28 insertions(+), 18 deletions(-)
diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c
index 24c74c60c093..37e2cac8e8b0 100644
--- a/drivers/vhost/vhost.c
+++ b/drivers/vho
This is used to hide the metadata address from virtqueue helpers. This
will allow to implement a vmap based fast accessing to metadata.
Signed-off-by: Jason Wang
---
drivers/vhost/vhost.c | 94 +++
1 file changed, 77 insertions(+), 17 deletions(-)
diff --
It was noticed that the copy_user() friends that was used to access
virtqueue metdata tends to be very expensive for dataplane
implementation like vhost since it involves lots of software checks,
speculation barrier, hardware feature toggling (e.g SMAP). The
extra cost will be more obvious when tra
On Wed, 23 Jan 2019 17:43:58 +0800
YueHaibing wrote:
> On 2019/1/23 17:12, Boris Brezillon wrote:
> > On Wed, 23 Jan 2019 14:58:27 +0800
> > YueHaibing wrote:
> >
> >> Fix a static code checker warning:
> >> drivers/mtd/devices/docg3.c:1875
> >> doc_probe_device() warn: passing zero to 'ERR_
This patch introduces the support for VIRTIO_F_ORDER_PLATFORM.
If this feature is negotiated, the driver must use the barriers
suitable for hardware devices. Otherwise, the device and driver
are assumed to be implemented in software, that is they can be
assumed to run on identical CPUs in an SMP co
On Mon, Nov 12, 2018 at 10:23 PM Hans Verkuil wrote:
>
> On 10/22/2018 04:49 PM, Tomasz Figa wrote:
> > Due to complexity of the video encoding process, the V4L2 drivers of
> > stateful encoder hardware require specific sequences of V4L2 API calls
> > to be followed. These include capability enume
On Tue, Jan 22, 2019 at 06:18:31PM +, Patrick Bellasi wrote:
> On 22-Jan 18:13, Peter Zijlstra wrote:
> > On Tue, Jan 15, 2019 at 10:15:05AM +, Patrick Bellasi wrote:
> > > @@ -342,11 +350,24 @@ static void sugov_iowait_boost(struct sugov_cpu
> > > *sg_cpu, u64 time,
> > > return
On Wed, 23 Jan 2019 at 09:26, Dietmar Eggemann wrote:
>
> On 1/16/19 10:43 AM, Vincent Guittot wrote:
>
> [...]
>
> > +static inline u64 rq_clock_pelt(struct rq *rq)
> > +{
>
> Doesn't this function need
>
>lockdep_assert_held(&rq->lock);
>assert_clock_updated(rq);
originally, it was repl
When building some xtensa config, I hit the following warning:
drivers/staging/mt7621-dts/Kconfig:4:warning: 'BUILTIN_DTB' has wrong type.
'select' only accept arguments of bool and tristate type
It is due to some arch use BUILTIN_DTB as a flag for the need to builtin
dtb but xtensa use it as a s
On Tue 22-01-19 16:44:07, Oscar Salvador wrote:
> This is the same sort of error we saw in [1].
>
> Gigantic hugepages crosses several memblocks, so it can be
> that the page we get in scan_movable_pages() is a page-tail
> belonging to a 1G-hugepage.
> If that happens, page_hstate()->size_to_hstat
From: yuzhoujian
We can monitor the sum wait time of a task group since 'commit 3d6c50c27bd6
("sched/debug: Show the sum wait time of a task group")'. However this
wait_sum just represents the confilct between different task groups, since
it is simply sum the wait time of task_group's cfs_rq. And
On 2019/1/23 17:12, Boris Brezillon wrote:
> On Wed, 23 Jan 2019 14:58:27 +0800
> YueHaibing wrote:
>
>> Fix a static code checker warning:
>> drivers/mtd/devices/docg3.c:1875
>> doc_probe_device() warn: passing zero to 'ERR_PTR'
>>
>> Fixes: ae9d4934b2d7 ("mtd: docg3: add multiple floor suppo
On Tue, Jan 22, 2019 at 7:10 PM Paul Kocialkowski
wrote:
>
> Hi,
>
> On Tue, 2019-01-22 at 17:19 +0900, Tomasz Figa wrote:
> > Hi Paul,
> >
> > On Fri, Dec 7, 2018 at 5:30 PM Paul Kocialkowski
> > wrote:
> > > Hi,
> > >
> > > Thanks for this new version! I only have one comment left, see below.
>
On Tue, Jan 22, 2019 at 04:21:16PM +0100, Greg Kroah-Hartman wrote:
> When calling debugfs functions, there is no need to ever check the
> return value. The function can work or not, but the code logic should
> never do something different based on this.
>
> Cc: Borislav Petkov
> Cc: Mauro Carva
On 1/22/19 6:41 AM, Greg Kroah-Hartman wrote:
When calling debugfs functions, there is no need to ever check the
return value. The function can work or not, but the code logic should
never do something different based on this.
Cc: Russell King
Cc: Jinbum Park
Cc: Kees Cook
Cc: Laura Abbott
On Tue, 2019-01-22 at 16:33 -0800, Florian Fainelli wrote:
> Hi Philipp,
>
> These two patches fix some recent issues brought up by Paul and Randy,
> feel free to squash into c196cdc7659d ("reset: Add Broadcom STB SW_INIT
> reset controller driver") since this is only in reset/next and
> linux-nex
801 - 900 of 980 matches
Mail list logo
