On Thu, Feb 18, 2016 at 12:16:47PM -0800, tip-bot for Dave Hansen wrote:
> Commit-ID: 35e97790f5f1e5cf2b5522c55e3e31d5c81bd226
> Gitweb: http://git.kernel.org/tip/35e97790f5f1e5cf2b5522c55e3e31d5c81bd226
> Author: Dave Hansen
> AuthorDate: Fri, 12 Feb 2016
On Thu, Feb 18, 2016 at 12:16:47PM -0800, tip-bot for Dave Hansen wrote:
> Commit-ID: 35e97790f5f1e5cf2b5522c55e3e31d5c81bd226
> Gitweb: http://git.kernel.org/tip/35e97790f5f1e5cf2b5522c55e3e31d5c81bd226
> Author: Dave Hansen
> AuthorDate: Fri, 12 Feb 2016 13:02:00 -0800
> Committer:
On Thu, Feb 18, 2016 at 11:41:59AM -0500, Johannes Weiner wrote:
> In machines with 140G of memory and enterprise flash storage, we have
> seen read and write bursts routinely exceed the kswapd watermarks and
> cause thundering herds in direct reclaim. Unfortunately, the only way
> to tune kswapd
On Thu, Feb 18, 2016 at 11:41:59AM -0500, Johannes Weiner wrote:
> In machines with 140G of memory and enterprise flash storage, we have
> seen read and write bursts routinely exceed the kswapd watermarks and
> cause thundering herds in direct reclaim. Unfortunately, the only way
> to tune kswapd
On 14/02/2016 12:31, Xiao Guangrong wrote:
> The array, gfn_track[mode][gfn], is introduced in memory slot for every
> guest page, this is the tracking count for the gust page on different
> modes. If the page is tracked then the count is increased, the page is
> not tracked after the count
On 14/02/2016 12:31, Xiao Guangrong wrote:
> The array, gfn_track[mode][gfn], is introduced in memory slot for every
> guest page, this is the tracking count for the gust page on different
> modes. If the page is tracked then the count is increased, the page is
> not tracked after the count
platform_driver does not need to set an owner, it will be populated by
the driver core.
Generated-by: scripts/coccinelle/api/platform_no_drv_owner.cocci
Signed-off-by: Amitoj Kaur Chawla
---
drivers/net/ethernet/ibm/ehea/ehea_main.c | 1 -
1 file changed, 1 deletion(-)
platform_driver does not need to set an owner, it will be populated by
the driver core.
Generated-by: scripts/coccinelle/api/platform_no_drv_owner.cocci
Signed-off-by: Amitoj Kaur Chawla
---
drivers/net/ethernet/ibm/ehea/ehea_main.c | 1 -
1 file changed, 1 deletion(-)
diff --git
On Fri, Feb 19, 2016 at 1:10 PM, Borislav Petkov wrote:
> On Fri, Feb 19, 2016 at 01:00:35PM +0200, Andy Shevchenko wrote:
>> That what I see last with earlycon enabled + `debug` in cmdline:
>
> That doesn't help.
Heh, rebuilt on clean repository -> everything works. Looks like
On Fri, Feb 19, 2016 at 1:10 PM, Borislav Petkov wrote:
> On Fri, Feb 19, 2016 at 01:00:35PM +0200, Andy Shevchenko wrote:
>> That what I see last with earlycon enabled + `debug` in cmdline:
>
> That doesn't help.
Heh, rebuilt on clean repository -> everything works. Looks like false
alarm and
On 14/02/2016 12:31, Xiao Guangrong wrote:
> Split rmap_write_protect() and introduce the function to abstract the write
> protection based on the slot
>
> This function will be used in the later patch
>
> Signed-off-by: Xiao Guangrong
> ---
>
On 14/02/2016 12:31, Xiao Guangrong wrote:
> Split rmap_write_protect() and introduce the function to abstract the write
> protection based on the slot
>
> This function will be used in the later patch
>
> Signed-off-by: Xiao Guangrong
> ---
> arch/x86/kvm/mmu.c | 16 +++-
>
The issue you are reporting looks like one we improved on android by using
the average pstate instead of using the last requested pstate
We know that this is improving the ffmpeg encoding performance when using the
load algorithm.
see patch attached
This patch is only applied on
The issue you are reporting looks like one we improved on android by using
the average pstate instead of using the last requested pstate
We know that this is improving the ffmpeg encoding performance when using the
load algorithm.
see patch attached
This patch is only applied on
On Fri, Feb 19, 2016 at 01:00:35PM +0200, Andy Shevchenko wrote:
> That what I see last with earlycon enabled + `debug` in cmdline:
That doesn't help. Can you dump RIP, etc registers as to where the
machine freezes?
Let me confirm this: booting with "dis_ucode_ldr" works?
Also, please send
On Fri, Feb 19, 2016 at 01:00:35PM +0200, Andy Shevchenko wrote:
> That what I see last with earlycon enabled + `debug` in cmdline:
That doesn't help. Can you dump RIP, etc registers as to where the
machine freezes?
Let me confirm this: booting with "dis_ucode_ldr" works?
Also, please send
On 14/02/2016 12:31, Xiao Guangrong wrote:
> Abstract the common operations from account_shadowed() and
> unaccount_shadowed(), then introduce kvm_mmu_gfn_disallow_lpage()
> and kvm_mmu_gfn_allow_lpage()
>
> These two functions will be used by page tracking in the later patch
>
>
On 14/02/2016 12:31, Xiao Guangrong wrote:
> Abstract the common operations from account_shadowed() and
> unaccount_shadowed(), then introduce kvm_mmu_gfn_disallow_lpage()
> and kvm_mmu_gfn_allow_lpage()
>
> These two functions will be used by page tracking in the later patch
>
>
On 14/02/2016 12:31, Xiao Guangrong wrote:
> kvm_lpage_info->write_count is used to detect if the large page mapping
> for the gfn on the specified level is allowed, rename it to disallow_lpage
> to reflect its purpose, also we rename has_wrprotected_page() to
> mmu_gfn_lpage_is_disallowed() to
On 14/02/2016 12:31, Xiao Guangrong wrote:
> kvm_lpage_info->write_count is used to detect if the large page mapping
> for the gfn on the specified level is allowed, rename it to disallow_lpage
> to reflect its purpose, also we rename has_wrprotected_page() to
> mmu_gfn_lpage_is_disallowed() to
Hi Lv,
On 02/19/2016 05:58 AM, Zheng, Lv wrote:
> Hi,
>
>> From: Peter Hurley [mailto:pe...@hurleysoftware.com]
>> Subject: Re: [PATCH v3 1/5] ACPI: change __init to __ref for
>> early_acpi_os_unmap_memory()
>>
>> On 02/17/2016 07:36 PM, Zheng, Lv wrote:
>>> Hi,
>>>
From: Aleksey Makarov
Hi Lv,
On 02/19/2016 05:58 AM, Zheng, Lv wrote:
> Hi,
>
>> From: Peter Hurley [mailto:pe...@hurleysoftware.com]
>> Subject: Re: [PATCH v3 1/5] ACPI: change __init to __ref for
>> early_acpi_os_unmap_memory()
>>
>> On 02/17/2016 07:36 PM, Zheng, Lv wrote:
>>> Hi,
>>>
From: Aleksey Makarov
On Fri, Feb 19, 2016 at 12:50 PM, Andy Shevchenko
wrote:
> On Fri, Feb 19, 2016 at 12:46 PM, Borislav Petkov wrote:
>> On Fri, Feb 19, 2016 at 12:33:46PM +0200, Andy Shevchenko wrote:
>>> commit 84aba677f009e20185aea322563389ad56e0ef7e
>>> Author:
On Fri, Feb 19, 2016 at 12:50 PM, Andy Shevchenko
wrote:
> On Fri, Feb 19, 2016 at 12:46 PM, Borislav Petkov wrote:
>> On Fri, Feb 19, 2016 at 12:33:46PM +0200, Andy Shevchenko wrote:
>>> commit 84aba677f009e20185aea322563389ad56e0ef7e
>>> Author: Boris Ostrovsky
>>> Date: Tue Feb 16
Sometimes when setting a breakpoint a process doesn't stop on it.
This is because the debug registers are not loaded correctly on
VCPU load.
The following simple reproducer from Oleg Nesterov tries using debug
registers in two threads. To see the bug, run a 2-VCPU guest under
"taskset -c 0",
Sometimes when setting a breakpoint a process doesn't stop on it.
This is because the debug registers are not loaded correctly on
VCPU load.
The following simple reproducer from Oleg Nesterov tries using debug
registers in two threads. To see the bug, run a 2-VCPU guest under
"taskset -c 0",
Hello Wei,
On 19/02/16 07:24, Wei Huang wrote:
On 02/11/2016 09:33 AM, Julien Grall wrote:
[...]
This is also dropping arch_timer_get_timecounter as it was only used by
the KVM code. Furthermore, a stub for the new helper hasn't been
introduced because KVM is requiring the arch timer for
Hello Wei,
On 19/02/16 07:24, Wei Huang wrote:
On 02/11/2016 09:33 AM, Julien Grall wrote:
[...]
This is also dropping arch_timer_get_timecounter as it was only used by
the KVM code. Furthermore, a stub for the new helper hasn't been
introduced because KVM is requiring the arch timer for
+ adding davinci maintainers to the loop.
Hi Andrew,
Not sure which tree should take the patch, but we needs acks from the
mach-davinci maitainers.
Other option is to defer this patch till other 6 patches are merged into
mainline.
--srini
On 18/02/16 23:17, Andrew Lunn wrote:
Now that
+ adding davinci maintainers to the loop.
Hi Andrew,
Not sure which tree should take the patch, but we needs acks from the
mach-davinci maitainers.
Other option is to defer this patch till other 6 patches are merged into
mainline.
--srini
On 18/02/16 23:17, Andrew Lunn wrote:
Now that
On Thu, Feb 18, 2016 at 06:13:57PM +, Catalin Marinas wrote:
> On Thu, Feb 18, 2016 at 06:03:54PM +, Will Deacon wrote:
> > On Thu, Feb 18, 2016 at 05:54:47PM +, Catalin Marinas wrote:
> > > On Thu, Feb 18, 2016 at 05:27:38PM +, Mark Rutland wrote:
> > > > @@ -145,6 +146,7 @@
On Thu, Feb 18, 2016 at 06:13:57PM +, Catalin Marinas wrote:
> On Thu, Feb 18, 2016 at 06:03:54PM +, Will Deacon wrote:
> > On Thu, Feb 18, 2016 at 05:54:47PM +, Catalin Marinas wrote:
> > > On Thu, Feb 18, 2016 at 05:27:38PM +, Mark Rutland wrote:
> > > > @@ -145,6 +146,7 @@
On Fri, Feb 19, 2016 at 12:46 PM, Borislav Petkov wrote:
> On Fri, Feb 19, 2016 at 12:33:46PM +0200, Andy Shevchenko wrote:
>> No, the commit 84aba677f009 as of today's linux-next on which I commented.
>
> You commented under the "> A subsequent commit, fbae4ba8c4a3" which
On Fri, Feb 19, 2016 at 12:46 PM, Borislav Petkov wrote:
> On Fri, Feb 19, 2016 at 12:33:46PM +0200, Andy Shevchenko wrote:
>> No, the commit 84aba677f009 as of today's linux-next on which I commented.
>
> You commented under the "> A subsequent commit, fbae4ba8c4a3" which confused
> me
> as to
On Thu, Feb 18, 2016 at 01:09:26PM -0800, Doug Smythies wrote:
> On 2106.02.18 Rafael J. Wysocki wrote:
> On Thu, Feb 18, 2016 at 12:11 PM, Mel Gorman wrote:
> >>
> >> Signed-off-by: Mel Gorman
> >> ---
> >> drivers/cpufreq/intel_pstate.c | 2 +-
> >> 1 file changed,
On Thu, Feb 18, 2016 at 01:09:26PM -0800, Doug Smythies wrote:
> On 2106.02.18 Rafael J. Wysocki wrote:
> On Thu, Feb 18, 2016 at 12:11 PM, Mel Gorman wrote:
> >>
> >> Signed-off-by: Mel Gorman
> >> ---
> >> drivers/cpufreq/intel_pstate.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1
Hi Peter,
Thank you for review.
On 02/19/2016 01:19 AM, Peter Hurley wrote:
> On 02/15/2016 10:05 AM, Aleksey Makarov wrote:
[..]
>> diff --git a/drivers/tty/serial/serial_core.c
>> b/drivers/tty/serial/serial_core.c
>> index a126a60..459ab54 100644
>> --- a/drivers/tty/serial/serial_core.c
Hi Peter,
Thank you for review.
On 02/19/2016 01:19 AM, Peter Hurley wrote:
> On 02/15/2016 10:05 AM, Aleksey Makarov wrote:
[..]
>> diff --git a/drivers/tty/serial/serial_core.c
>> b/drivers/tty/serial/serial_core.c
>> index a126a60..459ab54 100644
>> --- a/drivers/tty/serial/serial_core.c
On 18/02/2016 10:57, John Garry wrote:
On 18/02/2016 10:30, Hannes Reinecke wrote:
On 02/18/2016 11:12 AM, John Garry wrote:
On 18/02/2016 07:40, Hannes Reinecke wrote:
[ .. ]
Well, the classical thing would be to associate each request tag
with a SAS task; or, in your case, associate each
On 02/19/2016 12:10 PM, Peter Rosin wrote:
Hi!
I'm looking at this code in drivers/media/dvb-frontends/m88ds3103.c in
the m88ds3103_set_frontend() function, line 600 (give or take):
s32tmp = 0x1 * (tuner_frequency - c->frequency);
s32tmp = DIV_ROUND_CLOSEST(s32tmp,
On 18/02/2016 10:57, John Garry wrote:
On 18/02/2016 10:30, Hannes Reinecke wrote:
On 02/18/2016 11:12 AM, John Garry wrote:
On 18/02/2016 07:40, Hannes Reinecke wrote:
[ .. ]
Well, the classical thing would be to associate each request tag
with a SAS task; or, in your case, associate each
On 02/19/2016 12:10 PM, Peter Rosin wrote:
Hi!
I'm looking at this code in drivers/media/dvb-frontends/m88ds3103.c in
the m88ds3103_set_frontend() function, line 600 (give or take):
s32tmp = 0x1 * (tuner_frequency - c->frequency);
s32tmp = DIV_ROUND_CLOSEST(s32tmp,
On Fri, Feb 19, 2016 at 12:33:46PM +0200, Andy Shevchenko wrote:
> No, the commit 84aba677f009 as of today's linux-next on which I commented.
You commented under the "> A subsequent commit, fbae4ba8c4a3" which confused me
as to which commit is the culprit.
> commit
On Fri, Feb 19, 2016 at 12:33:46PM +0200, Andy Shevchenko wrote:
> No, the commit 84aba677f009 as of today's linux-next on which I commented.
You commented under the "> A subsequent commit, fbae4ba8c4a3" which confused me
as to which commit is the culprit.
> commit
Hi Peter,
Thank you for review.
On 02/19/2016 01:03 AM, Peter Hurley wrote:
> On 02/17/2016 07:36 PM, Zheng, Lv wrote:
>> Hi,
>>
>>> From: Aleksey Makarov [mailto:aleksey.maka...@linaro.org]
>>> Subject: Re: [PATCH v3 1/5] ACPI: change __init to __ref for
>>> early_acpi_os_unmap_memory()
>>>
>>>
Hi Peter,
Thank you for review.
On 02/19/2016 01:03 AM, Peter Hurley wrote:
> On 02/17/2016 07:36 PM, Zheng, Lv wrote:
>> Hi,
>>
>>> From: Aleksey Makarov [mailto:aleksey.maka...@linaro.org]
>>> Subject: Re: [PATCH v3 1/5] ACPI: change __init to __ref for
>>> early_acpi_os_unmap_memory()
>>>
>>>
Linus,
please pull sound fixes for v4.5-rc5 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
tags/sound-4.5-rc5
The topmost commit is 67ec1072b053c15564e6090ab30127895dc77a89
sound fixes for 4.5-rc5
this
Linus,
please pull sound fixes for v4.5-rc5 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
tags/sound-4.5-rc5
The topmost commit is 67ec1072b053c15564e6090ab30127895dc77a89
sound fixes for 4.5-rc5
this
On Fri, Feb 19, 2016 at 12:18 PM, Borislav Petkov wrote:
> On Fri, Feb 19, 2016 at 12:06:33PM +0200, Andy Shevchenko wrote:
>> Sorry for being too late, but this commit breaks 32-bit kernel on
>> Intel Medfield. Reverting the only commit from today's linux-next
>> helps.
>
> You
On Fri, Feb 19, 2016 at 12:18 PM, Borislav Petkov wrote:
> On Fri, Feb 19, 2016 at 12:06:33PM +0200, Andy Shevchenko wrote:
>> Sorry for being too late, but this commit breaks 32-bit kernel on
>> Intel Medfield. Reverting the only commit from today's linux-next
>> helps.
>
> You mean this
On Fri, Feb 19, 2016 at 10:30:09AM +0800, Zhi-zhou wrote:
> On Thu, Feb 18, 2016 at 7:58 PM, Catalin Marinas
> wrote:
> >
> > On Thu, Feb 18, 2016 at 07:48:35PM +0800, Zhi-zhou Zhang wrote:
> > > From: zhizhou
> > >
> > > This patch is based on the
On Friday 19 February 2016 09:22:44 Marek Szyprowski wrote:
> This patch replaces ARM-specific IOMMU-based DMA-mapping implementation
> with generic IOMMU DMA-mapping code shared with ARM64 architecture. The
> side-effect of this change is a switch from bitmap-based IO address space
> management
On Fri, Feb 19, 2016 at 10:30:09AM +0800, Zhi-zhou wrote:
> On Thu, Feb 18, 2016 at 7:58 PM, Catalin Marinas
> wrote:
> >
> > On Thu, Feb 18, 2016 at 07:48:35PM +0800, Zhi-zhou Zhang wrote:
> > > From: zhizhou
> > >
> > > This patch is based on the implementation of arm. The generic
> > >
On Friday 19 February 2016 09:22:44 Marek Szyprowski wrote:
> This patch replaces ARM-specific IOMMU-based DMA-mapping implementation
> with generic IOMMU DMA-mapping code shared with ARM64 architecture. The
> side-effect of this change is a switch from bitmap-based IO address space
> management
Don't print out an error with the driver sees EPROBE_DEFER when
attempting to get the gpio. These errors are usually transient; the
probe will be retried later.
Signed-off-by: Rabin Vincent
---
drivers/regulator/gpio-regulator.c | 6 --
1 file changed, 4
Don't print out an error with the driver sees EPROBE_DEFER when
attempting to get the gpio. These errors are usually transient; the
probe will be retried later.
Signed-off-by: Rabin Vincent
---
drivers/regulator/gpio-regulator.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff
Hi, Biederman
> -Original Message-
> From: Eric W. Biederman [mailto:ebied...@xmission.com]
> Sent: Friday, February 19, 2016 4:18 AM
> To: Zhao Lei
> Cc: 'Mateusz Guzik' ;
> contain...@lists.linux-foundation.org; linux-kernel@vger.kernel.org
>
Hi, Biederman
> -Original Message-
> From: Eric W. Biederman [mailto:ebied...@xmission.com]
> Sent: Friday, February 19, 2016 4:18 AM
> To: Zhao Lei
> Cc: 'Mateusz Guzik' ;
> contain...@lists.linux-foundation.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] Make core_pattern
On Tue, Feb 16, 2016 at 10:39:05PM -0800, shalin mehta wrote:
> Hello,
>
> Should I send this patch again due the spelling mistake in the patch
> description?
>
Yes. And put what Oleg Drokin said about it worked because there were
no users in the changelog.
regards,
dan carpenter
On Tue, Feb 16, 2016 at 10:39:05PM -0800, shalin mehta wrote:
> Hello,
>
> Should I send this patch again due the spelling mistake in the patch
> description?
>
Yes. And put what Oleg Drokin said about it worked because there were
no users in the changelog.
regards,
dan carpenter
On 02/18/2016, 06:44 PM, Tejun Heo wrote:
> Hello,
>
> Can you please do the followings?
>
> 1. Remove WQ_MEM_RECLAIM from the affected workqueue and see whether
>the problem is reproducible. WQ_MEM_RECLAIM on anything bluetooth
>doesn't make sense btw. Why is it there?
>
> 2. If
On 02/18/2016, 06:44 PM, Tejun Heo wrote:
> Hello,
>
> Can you please do the followings?
>
> 1. Remove WQ_MEM_RECLAIM from the affected workqueue and see whether
>the problem is reproducible. WQ_MEM_RECLAIM on anything bluetooth
>doesn't make sense btw. Why is it there?
>
> 2. If
On Friday 19 February 2016 08:47:47 Vladimir Murzin wrote:
> Ah, it explains why my quick attempt to enable BE for MPS2 (M-class
> platform) failed. With this patch applied I'm able to see Linux booting
> on MPS2 FVP model in BE, not complete boot but it might be due to other
> reasons. So this
On Friday 19 February 2016 08:47:47 Vladimir Murzin wrote:
> Ah, it explains why my quick attempt to enable BE for MPS2 (M-class
> platform) failed. With this patch applied I'm able to see Linux booting
> on MPS2 FVP model in BE, not complete boot but it might be due to other
> reasons. So this
When computing the residue we need two pieces of information: the current
descriptor and the remaining data of the current descriptor. To get
that information, we need to read consecutively two registers but we
can't do it in an atomic way. For that reason, we have to check manually
that current
When computing the residue we need two pieces of information: the current
descriptor and the remaining data of the current descriptor. To get
that information, we need to read consecutively two registers but we
can't do it in an atomic way. For that reason, we have to check manually
that current
Hi Vincent,
On Fri, Feb 19, 2016 at 12:31:17AM +0100, Vincent Stehlé wrote:
> Compile hyp-stub explicitly for arm v7-a. This fixes the following build
> errors:
>
> arch/arm/kernel/hyp-stub.S: Assembler messages:
> arch/arm/kernel/hyp-stub.S:168: Error: selected processor does not support
>
On Fri, Feb 19, 2016 at 12:06:33PM +0200, Andy Shevchenko wrote:
> Sorry for being too late, but this commit breaks 32-bit kernel on
> Intel Medfield. Reverting the only commit from today's linux-next
> helps.
You mean this commit?!
fbae4ba8c4a3 ("x86, microcode: Reload microcode on resume")
Hi Vincent,
On Fri, Feb 19, 2016 at 12:31:17AM +0100, Vincent Stehlé wrote:
> Compile hyp-stub explicitly for arm v7-a. This fixes the following build
> errors:
>
> arch/arm/kernel/hyp-stub.S: Assembler messages:
> arch/arm/kernel/hyp-stub.S:168: Error: selected processor does not support
>
On Fri, Feb 19, 2016 at 12:06:33PM +0200, Andy Shevchenko wrote:
> Sorry for being too late, but this commit breaks 32-bit kernel on
> Intel Medfield. Reverting the only commit from today's linux-next
> helps.
You mean this commit?!
fbae4ba8c4a3 ("x86, microcode: Reload microcode on resume")
Of course, we still reach almost the same maximum stack usage as before
because we're going to put the function on stack in the end anyway.
regards,
dan carpenter
Of course, we still reach almost the same maximum stack usage as before
because we're going to put the function on stack in the end anyway.
regards,
dan carpenter
When lookuping nat entry in cache_nat_entry, if we fail to hit nat cache,
we try to load nat entries a) from journal of current segment cache or b)
from NAT pages for updating, during the process, write lock of
nat_tree_lock will be held to avoid inconsistent condition in between
nid cache and nat
When lookuping nat entry in cache_nat_entry, if we fail to hit nat cache,
we try to load nat entries a) from journal of current segment cache or b)
from NAT pages for updating, during the process, write lock of
nat_tree_lock will be held to avoid inconsistent condition in between
nid cache and nat
Hi!
I'm looking at this code in drivers/media/dvb-frontends/m88ds3103.c in
the m88ds3103_set_frontend() function, line 600 (give or take):
s32tmp = 0x1 * (tuner_frequency - c->frequency);
s32tmp = DIV_ROUND_CLOSEST(s32tmp, priv->mclk_khz);
if (s32tmp < 0)
Hi!
I'm looking at this code in drivers/media/dvb-frontends/m88ds3103.c in
the m88ds3103_set_frontend() function, line 600 (give or take):
s32tmp = 0x1 * (tuner_frequency - c->frequency);
s32tmp = DIV_ROUND_CLOSEST(s32tmp, priv->mclk_khz);
if (s32tmp < 0)
In curseg cache, f2fs caches two different parts:
- datas of current summay block, i.e. summary entries, footer info.
- journal info, i.e. sparse nat/sit entries or io stat info.
With this approach, 1) it may cause higher lock contention when we access
or update both of the parts of cache since
In curseg cache, f2fs caches two different parts:
- datas of current summay block, i.e. summary entries, footer info.
- journal info, i.e. sparse nat/sit entries or io stat info.
With this approach, 1) it may cause higher lock contention when we access
or update both of the parts of cache since
On Thu, Feb 11, 2016 at 5:13 PM, Boris Ostrovsky
wrote:
> Commit a18a0f6850d4 ("x86, microcode: Don't initialize microcode code on
> paravirt") added a paravirt test in microcode_init(), primarily to avoid
> making
On Thu, Feb 11, 2016 at 5:13 PM, Boris Ostrovsky
wrote:
> Commit a18a0f6850d4 ("x86, microcode: Don't initialize microcode code on
> paravirt") added a paravirt test in microcode_init(), primarily to avoid
> making mc_bp_resume()->load_ucode_ap()->check_loader_disabled_ap() calls
> On 32-bit
Hi Eddie,
On 19/02/16 07:00, Eddie Huang wrote:
MT8173 E1 chip has one bug that if turn off USB power domain, vcore
power will also be off, thus cause modules using vcore power domain
fail, like MMC. The E1 chip only found on MT8173-evb board and this
board only has E1 chip, so implement this
Hi Eddie,
On 19/02/16 07:00, Eddie Huang wrote:
MT8173 E1 chip has one bug that if turn off USB power domain, vcore
power will also be off, thus cause modules using vcore power domain
fail, like MMC. The E1 chip only found on MT8173-evb board and this
board only has E1 chip, so implement this
On 02/18/2016 09:04 PM, Jordan Hargrave wrote:
> The VPD-R is a readonly area of the PCI Vital Product Data region.
> There are some standard keywords for serial number, manufacturer,
> and vendor-specific values. Dell Servers use a vendor-specific
> tag to store number of ports and port mapping
On 02/18/2016 09:04 PM, Jordan Hargrave wrote:
> The VPD-R is a readonly area of the PCI Vital Product Data region.
> There are some standard keywords for serial number, manufacturer,
> and vendor-specific values. Dell Servers use a vendor-specific
> tag to store number of ports and port mapping
On Wed, Feb 17, 2016 at 09:32:52AM +0800, Nicolas Boichat wrote:
> This patch was first sent upstream here: https://lkml.org/lkml/2015/5/28/747,
> but was not picked up (probably because it was part of a bigger series that
> refactored binder).
Riley was supposed to resend it with a proper sign
On Wed, Feb 17, 2016 at 09:32:52AM +0800, Nicolas Boichat wrote:
> This patch was first sent upstream here: https://lkml.org/lkml/2015/5/28/747,
> but was not picked up (probably because it was part of a bigger series that
> refactored binder).
Riley was supposed to resend it with a proper sign
On Fri, Feb 19, 2016 at 11:45 AM, Vladimir Murzin
wrote:
> On 16/02/16 13:09, Vladimir Murzin wrote:
+EARLYCON_DECLARE(mps2, mps2_early_console_setup);
>> +OF_EARLYCON_DECLARE(mps2, "arm,mps2-uart", mps2_early_console_setup);
>>> >
>>> > IIRC Peter Hurley
On Fri, Feb 19, 2016 at 11:45 AM, Vladimir Murzin
wrote:
> On 16/02/16 13:09, Vladimir Murzin wrote:
+EARLYCON_DECLARE(mps2, mps2_early_console_setup);
>> +OF_EARLYCON_DECLARE(mps2, "arm,mps2-uart", mps2_early_console_setup);
>>> >
>>> > IIRC Peter Hurley mentioned you don't need to put
With below serials, we will lose parts of dirents:
1) mount f2fs with inline_dentry option
2) echo 1 > /sys/fs/f2fs/sdX/dir_level
3) mkdir dir
4) touch 180 files named [001-180] in dir
5) touch 181 in dir
6) echo 3 > /proc/sys/vm/drop_caches
7) ll dir
ls: cannot access 2: No such file or
With below serials, we will lose parts of dirents:
1) mount f2fs with inline_dentry option
2) echo 1 > /sys/fs/f2fs/sdX/dir_level
3) mkdir dir
4) touch 180 files named [001-180] in dir
5) touch 181 in dir
6) echo 3 > /proc/sys/vm/drop_caches
7) ll dir
ls: cannot access 2: No such file or
* Peter Zijlstra wrote:
> On Fri, Feb 19, 2016 at 08:58:43AM +0100, Ingo Molnar wrote:
> > > I prefer to use my modern console width to display multiple columns of
> > > text,
> > > instead of wasting it to display mostly whitespace. Therefore I still
> > > very much
>
* Peter Zijlstra wrote:
> On Fri, Feb 19, 2016 at 08:58:43AM +0100, Ingo Molnar wrote:
> > > I prefer to use my modern console width to display multiple columns of
> > > text,
> > > instead of wasting it to display mostly whitespace. Therefore I still
> > > very much
> > > prefer ~80 char
2016-02-17 2:11 GMT+09:00 Catalin Marinas :
> On Tue, Feb 16, 2016 at 04:44:38AM +, EunTaik Lee wrote:
>> diff --git a/arch/arm64/mm/fault.c b/arch/arm64/mm/fault.c
>> index 19211c4..a5ebb99 100644
>> --- a/arch/arm64/mm/fault.c
>> +++ b/arch/arm64/mm/fault.c
>> @@
2016-02-17 2:11 GMT+09:00 Catalin Marinas :
> On Tue, Feb 16, 2016 at 04:44:38AM +, EunTaik Lee wrote:
>> diff --git a/arch/arm64/mm/fault.c b/arch/arm64/mm/fault.c
>> index 19211c4..a5ebb99 100644
>> --- a/arch/arm64/mm/fault.c
>> +++ b/arch/arm64/mm/fault.c
>> @@ -371,6 +371,14 @@ static int
On 16/02/16 13:09, Vladimir Murzin wrote:
>>> +EARLYCON_DECLARE(mps2, mps2_early_console_setup);
>>> >> +OF_EARLYCON_DECLARE(mps2, "arm,mps2-uart", mps2_early_console_setup);
>> >
>> > IIRC Peter Hurley mentioned you don't need to put both anymore, OF_
>> > one is enough.
>> >
> I've just tried
On 16/02/16 13:09, Vladimir Murzin wrote:
>>> +EARLYCON_DECLARE(mps2, mps2_early_console_setup);
>>> >> +OF_EARLYCON_DECLARE(mps2, "arm,mps2-uart", mps2_early_console_setup);
>> >
>> > IIRC Peter Hurley mentioned you don't need to put both anymore, OF_
>> > one is enough.
>> >
> I've just tried
Marc,
On Thu, 18 Feb 2016 16:41:23 +, Marc Zyngier wrote:
> It looks really nice, except for a couple of points, see below.
Thanks again for the review.
> > +/*
> > + * We don't support the group events, so we simply have 8 interrupts
> > + * per frame.
> > + */
> > +#define
Marc,
On Thu, 18 Feb 2016 16:41:23 +, Marc Zyngier wrote:
> It looks really nice, except for a couple of points, see below.
Thanks again for the review.
> > +/*
> > + * We don't support the group events, so we simply have 8 interrupts
> > + * per frame.
> > + */
> > +#define
On Thu, 2016-02-18 at 18:59 +, Robin Murphy wrote:
> On 18/02/16 18:12, Jon Medhurst (Tixy) wrote:
> > On Thu, 2016-02-18 at 18:05 +0100, Arnd Bergmann wrote:
> >> build-testing with clang showed that the "J" constraint does not take
> >> positive arguments on clang when building in for
On Thu, 2016-02-18 at 18:59 +, Robin Murphy wrote:
> On 18/02/16 18:12, Jon Medhurst (Tixy) wrote:
> > On Thu, 2016-02-18 at 18:05 +0100, Arnd Bergmann wrote:
> >> build-testing with clang showed that the "J" constraint does not take
> >> positive arguments on clang when building in for
1201 - 1300 of 1436 matches
Mail list logo