Hi Linus,
I've one more bugfix for you for 4.12-rc6 to fix something that came up
in an earlier rc.
--Darrick
The following changes since commit 63db7c815bc0997c29e484d2409684fdd9fcd93b:
xfs: use ->b_state to fix buffer I/O accounting release race (2017-05-31
08:22:52 -0700)
are available i
On Fri, 16 Jun 2017, Joe Perches wrote:
> On Sat, 2017-06-17 at 08:00 +0200, Julia Lawall wrote:
> > On Fri, 16 Jun 2017, Joe Perches wrote:
> > > On Sat, 2017-06-17 at 07:23 +0200, Julia Lawall wrote:
> > > > On Fri, 16 Jun 2017, Joe Perches wrote:
> > > > > On Fri, 2017-06-16 at 19:45 +0200, F
On Sat, 2017-06-17 at 08:00 +0200, Julia Lawall wrote:
> On Fri, 16 Jun 2017, Joe Perches wrote:
> > On Sat, 2017-06-17 at 07:23 +0200, Julia Lawall wrote:
> > > On Fri, 16 Jun 2017, Joe Perches wrote:
> > > > On Fri, 2017-06-16 at 19:45 +0200, Frans Klaver wrote:
> > > > > The header field in stru
On Fri, Jun 16, 2017 at 11:03 AM, H.J. Lu wrote:
> On Fri, Jun 16, 2017 at 10:56 AM, Andy Lutomirski wrote:
>> On Fri, Jun 16, 2017 at 10:44 AM, H.J. Lu wrote:
>>> On Fri, Jun 16, 2017 at 9:38 AM, Andy Lutomirski wrote:
On Fri, Jun 16, 2017 at 9:17 AM, H.J. Lu wrote:
> On Fri, Jun 16,
On Fri, 16 Jun 2017, Joe Perches wrote:
> On Sat, 2017-06-17 at 07:23 +0200, Julia Lawall wrote:
> > On Fri, 16 Jun 2017, Joe Perches wrote:
> > > On Fri, 2017-06-16 at 19:45 +0200, Frans Klaver wrote:
> > > > The header field in struct pd_message is declared as an __le16 type. The
> > > > data
diff --git a/Makefile b/Makefile
index 94d663c935c0..ba5a70b6e32c 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 4
-SUBLEVEL = 72
+SUBLEVEL = 73
EXTRAVERSION =
NAME = Blurry Fish Butt
@@ -789,7 +789,7 @@ KBUILD_CFLAGS += $(call cc-option,-Werror=date-time)
KB
I'm announcing the release of the 4.4.73 kernel.
All users of the 4.4 kernel series must upgrade.
The updated 4.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.4.y
and can be browsed at the normal kernel.org git web browser:
2017-06-16 23:38 GMT+08:00 Radim Krčmář :
> 2017-06-16 22:24+0800, Wanpeng Li:
>> 2017-06-16 21:37 GMT+08:00 Radim Krčmář :
>> > 2017-06-14 19:26-0700, Wanpeng Li:
>> >> From: Wanpeng Li
>> >>
>> >> Add an async_page_fault field to vcpu->arch.exception to identify an async
>> >> page fault, and co
On Sat, 2017-06-17 at 07:23 +0200, Julia Lawall wrote:
> On Fri, 16 Jun 2017, Joe Perches wrote:
> > On Fri, 2017-06-16 at 19:45 +0200, Frans Klaver wrote:
> > > The header field in struct pd_message is declared as an __le16 type. The
> > > data in the message is supposed to be little endian. This
Le Sat, 17 Jun 2017 00:46:12 +0200,
Peter Rosin a écrit :
> Hm, it's probably too late to do it here. Planes have already been
> enabled and the engine may have started to fetch data and do the
> composition. You could do that in ->update_plane() [1], and make it a
> per-plane
On Fri, 16 Jun 2017, Joe Perches wrote:
> On Fri, 2017-06-16 at 19:45 +0200, Frans Klaver wrote:
> > The header field in struct pd_message is declared as an __le16 type. The
> > data in the message is supposed to be little endian. This means we don't
> > have to go and shift the individual bytes
Use the e820_table_ori instead of e820_table_firmware to check
the consistence of memory layout provided by BIOS, because the
e820_table_firmware might be modified by the kernel such as efi
boot stub. To be more specific, during bootup, the efi boot stub
might allocate memory via efi service for th
On Fri, Jun 16, 2017 at 06:15:29PM -0700, Dan Williams wrote:
> Refactor the core of generic_swapfile_activate() into bmap_walk() so
> that it can be used by a new daxfile_activate() helper (to be added).
No way in hell! generic_swapfile_activate needs to day and no new users
of ->bmap over my de
Currently we try to have e820_table_firmware to represent the
original firmware memory layout passed to us by the bootloader,
however it is not the case, the e820_table_firmware might still
be modified by linux:
1. During bootup, the efi boot stub might allocate memory via
efi service for the PC
This is a patch set to fix the issue found during hibernation restore that,
the MD5 fingerprint of the physical memory layout checking code has reported a
false-positive failure due to incorrect input from the e820 map.
Chen Yu (2):
x86/boot/e820: Introduce e820_table_ori to represent the real o
Michal Hocko wrote:
> On Fri 16-06-17 21:22:20, Tetsuo Handa wrote:
> > Michal Hocko wrote:
> > > OK, could you play with the patch/idea suggested in
> > > http://lkml.kernel.org/r/20170615122031.gl1...@dhcp22.suse.cz?
> >
> > I think we don't need to worry about mmap_sem dependency inside __mmput
On Thu, Jun 15, 2017 at 02:37:22PM -0600, Logan Gunthorpe wrote:
> This commit adds the code to initialize the memory windows in the
> hardware. This includes setting up the requester ID table, and
> figuring out which bar corresponds to which memory window. (Seeing
> the switch can be configured w
On Thu, Jun 15, 2017 at 02:37:20PM -0600, Logan Gunthorpe wrote:
> In order for the switchtec NTB code to handle link change events we
> create a notifier block in the switchtec code which gets called
> whenever an appropriate event interrupt occurs.
>
> In order to preserve userspace's ability to
On Thu, Jun 15, 2017 at 02:37:17PM -0600, Logan Gunthorpe wrote:
> Create the switchtec.h header in include/linux with hardware defines
> and the switchtec_dev structure moved directly from switchtec.c.
> This is a prep patch for created an NTB driver for switchtec.
>
> Signed-off-by: Logan Guntho
On Thu, Jun 15, 2017 at 02:37:18PM -0600, Logan Gunthorpe wrote:
> We switch to class_register/unregister and a declared class which
> is exported for use in the switchtec_ntb driver.
>
> Signed-off-by: Logan Gunthorpe
> Reviewed-by: Stephen Bates
> Reviewed-by: Kurt Schwemmer
> ---
> drivers/
On Fri, Jun 16, 2017 at 11:21:00PM +0300, Serge Semin wrote:
> On Fri, Jun 16, 2017 at 01:34:59PM -0600, Logan Gunthorpe
> wrote:
> > Now, if you'd like to actually review the code I'd be happy to address
> > any concerns you find. I won't be responding to any more philosophical
> > arguments or
On Fri, Jun 16, 2017 at 09:47:21PM +0200, Luis R. Rodriguez wrote:
> Some of the knobs however are for extending tests for
> existing APIs in older kernels, the async and custom fallback one are an
> example. There are a series of test cases later added which could help
> test LTS kernels. Would L
On Thu, Jun 15, 2017 at 04:42:04PM +0200, Jan Kara wrote:
> On Wed 14-06-17 11:22:09, Ross Zwisler wrote:
> > To be able to use the common 4k zero page in DAX we need to have our PTE
> > fault path look more like our PMD fault path where a PTE entry can be
> > marked as dirty and writeable as it is
Sys_pkey_alloc() allocates and returns available pkey
Sys_pkey_free() frees up the pkey.
Total 32 keys are supported on powerpc. However pkey 0,1 and 31
are reserved. So effectively we have 29 pkeys.
Signed-off-by: Ram Pai
---
arch/powerpc/Kconfig | 15
arch/power
Rearrange 64K PTE bits to free up bits 3, 4, 5 and 6
in the 64K backed hpte pages. This along with the earlier
patch will entirely free up the four bits from 64K PTE.
This patch does the following change to 64K PTE that is
backed by 64K hpte.
H_PAGE_F_SECOND which occupied bit 4 moves to the
Map the PTE protection key bits to the HPTE key protection bits,
while creatiing HPTE entries.
Signed-off-by: Ram Pai
---
arch/powerpc/include/asm/book3s/64/mmu-hash.h | 5 +
arch/powerpc/include/asm/pkeys.h | 7 +++
arch/powerpc/mm/hash_utils_64.c | 5 +
Signed-off-by: Ram Pai
---
arch/powerpc/include/asm/processor.h | 5 +
arch/powerpc/kernel/process.c| 18 ++
2 files changed, 23 insertions(+)
diff --git a/arch/powerpc/include/asm/processor.h
b/arch/powerpc/include/asm/processor.h
index a2123f2..1f714df 100644
---
The value of the AMR register at the time of exception
is made available in gp_regs[PT_AMR] of the siginfo.
This field can be used to reprogram the permission bits of
any valid pkey.
Similarly the value of the pkey, whose protection got violated,
is made available at si_pkey field of the siginfo
Replace the magic number used to check for DSI exception
with a meaningful value.
Signed-off-by: Ram Pai
---
arch/powerpc/include/asm/reg.h | 9 -
arch/powerpc/kernel/exceptions-64s.S | 2 +-
2 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc/include/asm/re
Added test support for PowerPC implementation off protection keys.
Signed-off-by: Ram Pai
---
tools/testing/selftests/vm/Makefile |1 +
tools/testing/selftests/vm/pkey-helpers.h | 365 +++
tools/testing/selftests/vm/protection_keys.c | 1451 +
tool
The Documentaton file is moved from x86 into the generic area,
since this feature is now supported by more than one archs.
Signed-off-by: Ram Pai
---
Documentation/vm/protection-keys.txt | 110 ++
Documentation/x86/protection-keys.txt | 85 --
Handle Data and Instruction exceptions caused by memory
protection-key.
Signed-off-by: Ram Pai
(cherry picked from commit a5e5217619a0c475fe0cacc3b0cf1d3d33c79a09)
Conflicts:
arch/powerpc/include/asm/reg.h
arch/powerpc/kernel/exceptions-64s.S
---
arch/powerpc/include/asm/mmu_con
This system call, associates the pkey with PTE of all
pages corresponding to the given address range.
Signed-off-by: Ram Pai
---
arch/powerpc/include/asm/book3s/64/pgtable.h | 22 ++-
arch/powerpc/include/asm/mman.h | 29 +
arch/powerpc/include/asm/pkeys.h |
Signed-off-by: Ram Pai
---
arch/powerpc/kernel/exceptions-64s.S | 16 ++--
1 file changed, 10 insertions(+), 6 deletions(-)
diff --git a/arch/powerpc/kernel/exceptions-64s.S
b/arch/powerpc/kernel/exceptions-64s.S
index 8db9ef8..a4de1b4 100644
--- a/arch/powerpc/kernel/exceptions-64s
Rearrange 64K PTE bits to free up bits 3, 4, 5 and 6
in the 4K backed hpte pages. These bits continue to be used
for 64K backed hpte pages in this patch, but will be freed
up in the next patch.
The patch does the following change to the 64K PTE format
H_PAGE_BUSY moves from bit 3 to bit 9
H_
Memory protection keys enable applications to protect its
address space from inadvertent access or corruption from
itself.
The overall idea:
A process allocates a key and associates it with
a address range withinits address space.
The process than can dynamically set read/wri
Hi all,
This is simple patchset for perf-config
to fix small bugs and refactor code.
I'd appreciate some feedback on this patchset.
The code is also available at 'config/refactoring-v4' branch on
git://github.com/taeung/linux-perf.git
Thanks,
Taeung
v4:
- rebase on current acme/perf/core
-
Currently only section->from_system_config is being checked multiple times.
items->from_system_config should be also checked, so fix it.
Cc: Jiri Olsa
Cc: Namhyung Kim
Signed-off-by: Taeung Song
---
tools/perf/builtin-config.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a
Currently set_config() can be repeatedly called for each
input config on the below case:
$ perf config kmem.default=slab report.children=false ...
But it's a waste, so finally write changed configs at a time.
Cc: Jiri Olsa
Cc: Namhyung Kim
Signed-off-by: Taeung Song
---
tools/perf/builtin-
To simplify the code related to 'ret' variable in cmd_config(),
initialize 'ret' with -1 instead of 0.
Cc: Jiri Olsa
Cc: Namhyung Kim
Signed-off-by: Taeung Song
---
tools/perf/builtin-config.c | 30 +-
1 file changed, 13 insertions(+), 17 deletions(-)
diff --git a/
show_spec_config() and set_config() can be called multiple times
in the loop in cmd_config().
However, The error cases of them wasn't checked, so fix it.
Reported-by: Arnaldo Carvalho de Melo
Cc: Jiri Olsa
Cc: Namhyung Kim
Signed-off-by: Taeung Song
---
tools/perf/builtin-config.c | 17 ++
Currently the users can not create a config file
in the below case.
Before:
$ rm -f ~/.perfconfig
$ perf config --user report.children=false
$ cat ~/.perfconfig
cat: /root/.perfconfig: No such file or directory
But I think it should work no matter whether a config file exists or not.
A
On 06/16/2017 05:41 PM, Jason A. Donenfeld wrote:
> Hi Lee,
>
> On Fri, Jun 16, 2017 at 11:58 PM, Lee Duncan wrote:
>> It seems like what you are doing is basically "good", i.e. if there is
>> not enough random data, don't use it. But what happens in that case? The
>> authentication fails? How do
Same as ip_gre, geneve and vxlan, use key->tos as traffic class value.
CC: Peter Dawson
Fixes: 0e9a709560db ("ip6_tunnel, ip6_gre: fix setting of DSCP on
encapsulated packets”)
Signed-off-by: Haishuang Yan
---
Changes since v3:
* Add fixes information
* Remove obsoleted RT_TOS mask
---
net
In collect_md mode, if the tun dev is down, it still can call
__ip6_tnl_rcv to receive on packets, and the rx statistics increase
improperly.
Fixes: 8d79266bc48c ("ip6_tunnel: add collect_md mode to IPv6 tunnels")
Cc: Alexei Starovoitov
Signed-off-by: Haishuang Yan
---
Change since v2:
* Fix
In collect_md mode, if the tun dev is down, it still can call
ip_tunnel_rcv to receive on packets, and the rx statistics increase
improperly.
Fixes: 2e15ea390e6f ("ip_gre: Add support to collect tunnel metadata.")
Cc: Pravin B Shelar
Signed-off-by: Haishuang Yan
---
Change since v2:
* Fix wro
Fixed checkpatch.pl warnings of "function definition argument FOO should
also have an identifier name"
Found using checkpatch
Signed-off-by: Derek Robson
V1 had vauge subjet
---
drivers/staging/rtl8192u/ieee80211/ieee80211.h | 2 +-
drivers/staging/rtl8192u/ieee80211/ieee80211_crypt.h | 4
Fixed checkpatch warnings "Use #include instead of "
Found using checkpatch
Signed-off-by: Derek Robson
V1 had vauge subject.
---
drivers/staging/rtl8723bs/include/osdep_service_linux.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/rtl8723bs/include/
Fixed style of permissions to octal.
Found using checkpatch
Signed-off-by: Derek Robson
V1 has vauge subject
---
drivers/staging/unisys/visorhba/visorhba_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/unisys/visorhba/visorhba_main.c
b/drivers/staging
> On 16 Jun 2017, at 10:44 PM, Daniel Borkmann wrote:
>
> On 06/15/2017 05:54 AM, Peter Dawson wrote:
>> On Thu, 15 Jun 2017 10:30:29 +0800
>> Haishuang Yan wrote:
>>
>>> Same as ip_gre, geneve and vxlan, use key->tos as tos value.
>>>
>>> CC: Peter Dawson
>>> Fixes: 0e9a709560db ("ip6_tunn
From: Len Brown
cpufreq_quick_get() allows cpufreq drivers to over-ride cpu_khz
that is otherwise reported in x86 /proc/cpuinfo "cpu MHz".
There are four problems with this scheme,
any of them is sufficient justification to delete it.
1. Depending on which cpufreq driver is loaded, the behavior
In-Reply-To:
Hi Rafael,
This patch series has 3 goals:
1. Make "cpu MHz" in /proc/cpuinfo supportable.
2. Make /sys/.../cpufreq/scaling_cur_freq meaningful
and consistent on modern x86 systems.
3. Use 1. and 2. to remove scheduler and cpufreq overhead
There are 3 main changes since this
From: Len Brown
The cpufreq/scaling_cur_freq sysfs attribute is now provided by
shared x86 cpufreq code on modern x86 systems, including
all systems supported by the intel_pstate driver.
In HWP mode, maintaining that value was the sole purpose of
the scheduler hook, intel_pstate_update_util_hwp(
From: Len Brown
When the governor is set to "performance", intel_pstate does not
need the scheduler hook for doing any calculations. Under these
conditions, its only purpose is to continue to maintain
cpufreq/scaling_cur_freq.
The cpufreq/scaling_cur_freq sysfs attribute is now provided by
shar
Fixed checkpatch.pl warnings of the form "function definition argument
'foo' should also have an identifier name" in header files.
Signed-off-by: Derek Robson
V1 had vague subject
---
drivers/staging/sm750fb/sm750.h | 24
1 file changed, 16 insertions(+), 8 deletions(-)
From: Len Brown
The goal of this change is to give users a uniform and meaningful
result when they read /sys/...cpufreq/scaling_cur_freq
on modern x86 hardware, as compared to what they get today.
Modern x86 processors include the hardware needed
to accurately calculate frequency over an interva
On Fri, 16 Jun 2017 11:24:07 -0700
Andrew Morton wrote:
> On Fri, 16 Jun 2017 16:57:14 +1000 Nicholas Piggin wrote:
>
> > After reconfiguring watchdog sysctls etc., architecture specific
> > watchdogs may not get all their parameters updated.
> >
> > watchdog_reconfigure() can be implemented t
Fix checkpatch.pl warnings of the form "function definition argument
'foo' should also have an identifier name" in header files.
Signed-off-by: Derek Robson
V1 and V2 had vague subject line
---
drivers/staging/vt6655/card.h| 30 ++---
drivers/staging/vt6655/channel.h | 4 +-
A couple of fixes; a leak in mntns_install() caught by Andrei
(this cycle regression) + d_invalidate() softlockup fix - that had
been reported by a bunch of people lately, but the problem is pretty
old.
The following changes since commit 32c1431eea4881a6b17bd7c639315010aeefa452:
Linux 4
Changed code indent to be tabs across whole driver
Found using checkpatch
Signed-off-by: Derek Robson
V1 had vague subject.
---
drivers/staging/ccree/ssi_cipher.c | 45 +-
drivers/staging/ccree/ssi_driver.c | 6 ++---
drivers/staging/ccree/ssi_driver.h
On Fri, 16 Jun 2017 11:21:17 -0700
Andrew Morton wrote:
> On Fri, 16 Jun 2017 16:57:12 +1000 Nicholas Piggin wrote:
>
> > For architectures that define HAVE_NMI_WATCHDOG, instead of having
> > them provide the complete touch_nmi_watchdog() function, just have
> > them provide arch_touch_nmi_wat
On Fri, Jun 16, 2017 at 07:29:00AM -0700, Richard Narron wrote:
> The 8 patches in the ufs-fixes group were applied to Linux 4.12-rc5.
> They seem to work fine with the simple testing that I do.
>
> I tested all 3 BSDs, FreeBSD 11.0, OpenBSD 6.1 and NetBSD 7.1 using 2
> filesystems, 44bsd (ufs1)
> On a second thought, in order to compute the frequency, user space
> needs to know the scaling and the max_pstate_physical value too, which
> may not be straightforward to obtain (on some Atoms, for example).
unless you run turbostat:-)
> So why don't we leave the tracepoint as is for now?
sur
On Thu, Jun 15, 2017 at 2:10 AM, Jan Kara wrote:
> I agree with moving ext4_xattr_rehash_entry() out of ext4_xattr_rehash().
> However how about just keeping ext4_xattr_rehash() in
> ext4_xattr_block_set() (so that you don't have to pass aditional argument
> to ext4_xattr_set_entry()) and calling
On Thu, Jun 15, 2017 at 12:57 AM, Jan Kara wrote:
> Hum, rather handle this similarly to how we handle delalloc reserved space.
> Add a callback to dq_ops to get "inode usage" of an inode and then use it
> in dquot_transfer(), dquot_free_inode(), dquot_alloc_inode().
I tried that approach by addi
On Fri, Jun 16, 2017 at 8:30 PM, Rafael J. Wysocki wrote:
> On Wednesday, June 07, 2017 07:39:13 PM Len Brown wrote:
>> From: Len Brown
>>
>> The goal of this change is to give users a uniform and meaningful
>> result when they read /sys/...cpufreq/scaling_cur_freq
>> on modern x86 hardware, as c
2017-06-16 23:38 GMT+08:00 Radim Krčmář :
> 2017-06-16 22:24+0800, Wanpeng Li:
>> 2017-06-16 21:37 GMT+08:00 Radim Krčmář :
>> > 2017-06-14 19:26-0700, Wanpeng Li:
>> >> From: Wanpeng Li
>> >>
>> >> Add an async_page_fault field to vcpu->arch.exception to identify an async
>> >> page fault, and co
On Sat, Jun 17, 2017 at 3:21 AM, Rafael J. Wysocki wrote:
> On Friday, June 16, 2017 09:10:39 PM Len Brown wrote:
>> >> >> - get_avg_frequency(cpu),
>> >> >> + aperfmperf_khz_on_cpu(cpu->cpu),
>> >>
>> >> Note that I deleted the line above in an updated version of this patc
sorry, that was a premature send...
>>> > What about update_turbo_pstate()?
>>> >
>>> > In theory MSR_IA32_MISC_ENABLE_TURBO_DISABLE can be set at any time, so
>>> > wouldn't that become problematic after this change?
>>>
>>> yes, the sysfs "no_turbo" attribute can be modified at any time, invokin
On Thu, 2017-06-08 at 20:38 +0200, Borislav Petkov wrote:
> On Fri, May 05, 2017 at 11:17:19AM -0700, Ricardo Neri wrote:
> > The feature User-Mode Instruction Prevention present in recent Intel
> > processor prevents a group of instructions from being executed with
> > CPL > 0. Otherwise, a genera
On Fri, Jun 16, 2017 at 9:06 PM, Rafael J. Wysocki wrote:
> On Friday, June 16, 2017 08:52:53 PM Len Brown wrote:
>> On Fri, Jun 16, 2017 at 8:04 PM, Rafael J. Wysocki
>> wrote:
>> > On Wednesday, June 07, 2017 07:39:15 PM Len Brown wrote:
>> >> From: Len Brown
>> >>
>> >> When the governor is
On Friday, June 16, 2017 09:10:39 PM Len Brown wrote:
> >> >> - get_avg_frequency(cpu),
> >> >> + aperfmperf_khz_on_cpu(cpu->cpu),
> >>
> >> Note that I deleted the line above in an updated version of this patch
> >> that I'm ready to send out.
> >>
> >> There were a couple
On Fri, Jun 16, 2017 at 8:09 PM, Rafael J. Wysocki wrote:
> On Wednesday, June 07, 2017 07:39:16 PM Len Brown wrote:
>> From: Len Brown
>>
>> The cpufreqa/scaling_cur_freq sysfs attribute is now provided by
>> the x86 cpufreq core on all modern x86 systems, including
>> all systems supported by t
Quoting PATCH 2/2:
To date, the full promise of byte-addressable access to persistent
memory has only been half realized via the filesystem-dax interface. The
current filesystem-dax mechanism allows an application to consume (read)
data from persistent storage at byte-size granular
Refactor the core of generic_swapfile_activate() into bmap_walk() so
that it can be used by a new daxfile_activate() helper (to be added).
There should be no functional differences as a result of this change,
although it does add the capability to perform the bmap with a given
page-size. This is i
To date, the full promise of byte-addressable access to persistent
memory has only been half realized via the filesystem-dax interface. The
current filesystem-dax mechanism allows an application to consume (read)
data from persistent storage at byte-size granularity, bypassing the
full page reads r
On Friday, June 16, 2017 08:52:53 PM Len Brown wrote:
> On Fri, Jun 16, 2017 at 8:04 PM, Rafael J. Wysocki wrote:
> > On Wednesday, June 07, 2017 07:39:15 PM Len Brown wrote:
> >> From: Len Brown
> >>
> >> When the governor is set to "performance", intel_pstate does not
> >> need the scheduler ho
>> >> - get_avg_frequency(cpu),
>> >> + aperfmperf_khz_on_cpu(cpu->cpu),
>>
>> Note that I deleted the line above in an updated version of this patch
>> that I'm ready to send out.
>>
>> There were a couple of problems with it.
>> The first is that it was ugly that tracing
On Fri, Jun 16, 2017 at 8:04 PM, Rafael J. Wysocki wrote:
> On Wednesday, June 07, 2017 07:39:15 PM Len Brown wrote:
>> From: Len Brown
>>
>> When the governor is set to "performance", intel_pstate does not
>> need the scheduler hook for doing any calculations. Under these
>> conditions, its onl
> On Fri, Jun 16, 2017 at 5:35 PM, Kani, Toshimitsu wrote:
> >> On Mon, Jun 12, 2017 at 3:25 PM, Toshi Kani wrote:
> >> > Sysfs "badblocks" information may be updated during run-time that:
> >> > - MCE, SCI, and sysfs "scrub" may add new bad blocks
> >> > - Writes and ioctl() may clear bad bloc
On Fri, Jun 16, 2017 at 5:35 PM, Kani, Toshimitsu wrote:
>> On Mon, Jun 12, 2017 at 3:25 PM, Toshi Kani wrote:
>> > Sysfs "badblocks" information may be updated during run-time that:
>> > - MCE, SCI, and sysfs "scrub" may add new bad blocks
>> > - Writes and ioctl() may clear bad blocks
>> >
>>
> On Fri, Jun 16, 2017 at 5:01 PM, Kani, Toshimitsu wrote:
> >> > --- a/drivers/acpi/nfit/core.c
> >> > +++ b/drivers/acpi/nfit/core.c
> >> > @@ -1031,7 +1031,7 @@ static ssize_t scrub_store(struct device *dev,
> >> > if (nd_desc) {
> >> > struct acpi_nfit_desc *acpi_desc =
On Friday, June 16, 2017 08:35:19 PM Len Brown wrote:
> On Fri, Jun 16, 2017 at 7:53 PM, Rafael J. Wysocki wrote:
> > On Wednesday, June 07, 2017 07:39:14 PM Len Brown wrote:
> >> From: Len Brown
> >>
> >> The x86 cpufreq core now uses aperfmperf_khz_on_cpu()
> >> to supply /sys/.../cpufreq/scali
Hi Lee,
On Fri, Jun 16, 2017 at 11:58 PM, Lee Duncan wrote:
> It seems like what you are doing is basically "good", i.e. if there is
> not enough random data, don't use it. But what happens in that case? The
> authentication fails? How does the user know to wait and try again?
The process just r
On Fri, Jun 16, 2017 at 4:35 PM, Sebastian Andrzej Siewior
wrote:
> I wouldn't just push the lock one up as is but move that write part to
> crng_init to remain within the locked section. Like that:
We can't quite do that, because invalidate_batched_entropy() needs to
be called _before_ crng_init
On Wednesday, June 07, 2017 07:39:13 PM Len Brown wrote:
> From: Len Brown
>
> The goal of this change is to give users a uniform and meaningful
> result when they read /sys/...cpufreq/scaling_cur_freq
> on modern x86 hardware, as compared to what they get today.
>
> Modern x86 processors includ
On Tue, May 23, 2017 at 03:23:57PM +0100, Gabriele Paoloni wrote:
> From: gabriele paoloni
>
> This patchset:
> 1) adds support for MSI interrupt vectors to be used for Roor Port services
> 2) adds support for DPC Root Port service interrupt
>
> The patchset has been tested on Hisilicon Hip08 Ch
> On Mon, Jun 12, 2017 at 3:25 PM, Toshi Kani wrote:
> > Sysfs "badblocks" information may be updated during run-time that:
> > - MCE, SCI, and sysfs "scrub" may add new bad blocks
> > - Writes and ioctl() may clear bad blocks
> >
> > Add support to send sysfs notifications to sysfs "badblocks"
On Fri, Jun 16, 2017 at 7:53 PM, Rafael J. Wysocki wrote:
> On Wednesday, June 07, 2017 07:39:14 PM Len Brown wrote:
>> From: Len Brown
>>
>> The x86 cpufreq core now uses aperfmperf_khz_on_cpu()
>> to supply /sys/.../cpufreq/scaling_cur_freq
>> on all x86 systems supporting APERF/MPERF.
>>
>> Th
On Wednesday, June 07, 2017 07:39:14 PM Len Brown wrote:
> From: Len Brown
>
> The x86 cpufreq core now uses aperfmperf_khz_on_cpu()
> to supply /sys/.../cpufreq/scaling_cur_freq
> on all x86 systems supporting APERF/MPERF.
>
> That includes 100% of systems supported by intel_pstate,
> and so in
On Wednesday, June 07, 2017 07:39:16 PM Len Brown wrote:
> From: Len Brown
>
> The cpufreqa/scaling_cur_freq sysfs attribute is now provided by
> the x86 cpufreq core on all modern x86 systems, including
> all systems supported by the intel_pstate driver.
Not sure what you mean by "x86 cpufreq c
On Wednesday, June 07, 2017 07:39:15 PM Len Brown wrote:
> From: Len Brown
>
> When the governor is set to "performance", intel_pstate does not
> need the scheduler hook for doing any calculations. Under these
> conditions, its only purpose is to continue to maintain
> cpufreq/scaling_cur_freq.
On Fri, Jun 16, 2017 at 5:01 PM, Kani, Toshimitsu wrote:
>> > --- a/drivers/acpi/nfit/core.c
>> > +++ b/drivers/acpi/nfit/core.c
>> > @@ -1031,7 +1031,7 @@ static ssize_t scrub_store(struct device *dev,
>> > if (nd_desc) {
>> > struct acpi_nfit_desc *acpi_desc = to_acpi_des
Utilize the asm-generic/fncpy.h implementation for ARM64 to allow the
use of drivers/misc/sram*.c on these platforms as well.
Signed-off-by: Florian Fainelli
---
arch/arm64/include/asm/Kbuild | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/include/asm/Kbuild b/arch/arm64/include/a
Now that ARM64 also has a fncpy() implementation, allow selection
SRAM_EXEC for ARM64 as well.
Signed-off-by: Florian Fainelli
---
drivers/misc/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
index 07bbd4cc1852..ac8779278c0c
Define a generic fncpy() implementation largely based on the ARM version
that requires an 8 bytes alignment for the destination address where to
copy this function as well as the function's own address.
Signed-off-by: Florian Fainelli
---
include/asm-generic/fncpy.h | 93
Hi all,
This patch series makes ARM's fncpy() implementation more generic (dropping the
Thumb-specifics) and available in an asm-generic header file.
Tested on a Broadcom ARM64 STB platform with code that is written to SRAM.
Changes in v3 (thanks Doug!):
- correct include guard names in asm-gene
In preparation for allowing a generic fncpy() implementation to live
under include/asm-generic/fncpy.h, rename the current include guards to
be __ASM_ARM_FNCPY_H, this also makes the header file more consistent
with other headers in the same directory.
Signed-off-by: Florian Fainelli
---
arch/ar
> > --- a/drivers/acpi/nfit/core.c
> > +++ b/drivers/acpi/nfit/core.c
> > @@ -1031,7 +1031,7 @@ static ssize_t scrub_store(struct device *dev,
> > if (nd_desc) {
> > struct acpi_nfit_desc *acpi_desc = to_acpi_desc(nd_desc);
> >
> > - rc = acpi_nfit_ars_rescan(a
On Fri, Jun 16, 2017 at 03:02:09PM +1000, NeilBrown wrote:
> When a loop device is being shutdown the backing file is
> closed with fput(). This is different from how close(2)
> closes files - it uses filp_close().
>
> The difference is important for filesystems which provide a ->flush
> file ope
1 - 100 of 798 matches
Mail list logo
