devm semantics arrange for resources to be torn down when
device-driver-probe fails or when device-driver-release completes.
Similar to devm_memremap_pages() there is no need to support an explicit
remove operation when the users properly adhere to devm semantics.
Note that devm_kzalloc() automati
Commit e8d513483300 "memremap: change devm_memremap_pages interface to
use struct dev_pagemap" refactored devm_memremap_pages() to allow a
dev_pagemap instance to be supplied. Passing in a dev_pagemap interface
simplifies the design of pgmap type drivers in that they can rely on
container_of() to l
The last step before devm_memremap_pages() returns success is to
allocate a release action, devm_memremap_pages_release(), to tear the
entire setup down. However, the result from devm_add_action() is not
checked.
Checking the error from devm_add_action() is not enough. The api
currently relies on
The routines hmm_devmem_add(), and hmm_devmem_add_resource() duplicated
devm_memremap_pages() and are now simple now wrappers around the core
facility to inject a dev_pagemap instance into the global pgmap_radix
and hook page-idle events. The devm_memremap_pages() interface is base
infrastructure f
In preparation for consolidating all ZONE_DEVICE enabling via
devm_memremap_pages(), teach it how to handle the constraints of
MEMORY_DEVICE_PRIVATE ranges.
Cc: Christoph Hellwig
Cc: "Jérôme Glisse"
Reported-by: Logan Gunthorpe
Reviewed-by: Logan Gunthorpe
Signed-off-by: Dan Williams
---
ker
On Thu, 13 Sep 2018 10:23:35 +0900 Masahiro Yamada wrote:
> Hello.
>
>
> Sorry if I am asking a stupid question.
>
>
> For arm64, there are only 2 cpu methods, psci and spin-table.
>
> Why do we still allow vendor-specific methods upstreamed
> for arm 32bit ports?
>
> To me, it looks like So
On Thu, Sep 13, 2018 at 9:51 AM wrote:
>
> >> From: Liu Song
> >>
> >> Although the 'need_to_create_worker' has been determined to be
> >> true before entering the function. However, adjusting the order
> >> of judgment can combine two judgments in the loop. Also improve
> >> the matching between
See vfs.git#work.tty-ioctl. Completely untested, should seriously
clean the things up wrt compat. Remaining problems (aside of the bugs
introduced in it, of course):
* TIOCSERGSTRUCT must die; it's present only in amiserial and it's
_vile_; look at what it copies out and weep.
On (09/12/18 15:33), Petr Mladek wrote:
> > console_trylock();
> > console_may_schedule = 0;
> > + if (exclusive_console) {
> > + exclusive_console = NULL;
> > + console_seq = rollback_console_seq;
>
> This might be controversial. Yes, it might help in some situations
This driver was originally written by ST in 2016 as a misc input device
driver, and hasn't been maintained for a long time. I grabbed some code
from it's API and reformed it into a iio proximity device driver.
This version of driver uses i2c bus to talk to the sensor and
polling for measuring compl
Hi Vinod,
After merging the slave-dma tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/dma/mcf-edma.c: In function 'mcf_edma_filter_fn':
drivers/dma/mcf-edma.c:296:33: warning: cast from pointer to integer of
different size [-Wpointer-to-int-cast]
return (mc
On Wed, Sep 12, 2018 at 05:01:02PM +0200, Arnd Bergmann wrote:
> Many drivers have ioctl() handlers that are completely compatible
> between 32-bit and 64-bit architectures, except for the argument
> that is passed down from user space and may have to be passed
> through compat_ptr() in order to be
$2Million Grant to you. Contact (cashgrant...@outlook.com) For Details
This email, including any attachments, is confidential and contains proprietary
content and may be legally privileged. This transmission is intended only for
the designated recipient(s), and any duplication or distribution, in
On Wed, Sep 12, 2018 at 04:28:28PM -0700, Andrew Morton wrote:
> On Tue, 28 Aug 2018 13:22:53 -0400 Johannes Weiner wrote:
>
> > There are several definitions of those functions/macros in places that
> > mess with fixed-point load averages. Provide an official version.
>
> missed blk-iolatency.c
Hi Randy,
Thanks for the report.
On Wed, Sep 12, 2018 at 05:45:08PM -0700, Randy Dunlap wrote:
> Multiple build errors when CONFIG_SMP is not set: (this is on i386 fwiw)
>
> in the psi (pressure) patches, I guess:
>
> In file included from ../kernel/sched/sched.h:1367:0,
> from
Compliment of the day to you Dear Friend.
Dear Friend.
I am Mrs. Amina Kadi. am sending this brief letter to solicit your
partnership to transfer $5.5 million US Dollars. I shall send you
more information and procedures when I receive positive response from
you.
Mrs. Amina Kadi
On Thu, Sep 13, 2018 at 12:05:51AM +0530, Himanshu Jha wrote:
> On Wed, Sep 12, 2018 at 10:20:34AM +0800, Song Qiang wrote:
> > This driver was originally written by ST in 2016 as a misc input device
> > driver, and hasn't been maintained for a long time. I grabbed some code
> > from it's API and r
Hello.
Sorry if I am asking a stupid question.
For arm64, there are only 2 cpu methods, psci and spin-table.
Why do we still allow vendor-specific methods upstreamed
for arm 32bit ports?
To me, it looks like SoC vendors continue inventing
different (but similar) ways to do the same thing.
It
On Wed, 2018-09-12 at 10:44 -0700, Kees Cook wrote:
> On Tue, Sep 11, 2018 at 8:36 PM, Bin Yang wrote:
> > persistent_ram_vmap() returns the page start vaddr.
> > persistent_ram_iomap() supports non-page-aligned mapping.
>
> Oh, yes, good catch. This should probably be explicitly mentioned in
> c
FYI, we noticed the following commit (built with gcc-6):
commit: 61224adcd25b0abd01f02459e82b30735161e723 ("ipc: Convert mqueue fs to
fs_context")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
in testcase: trinity
with following parameters:
runtime: 300s
test-
swab.h uses __always_inline without including the header where it is
defined, this is exposed by musl based distributions where this macro is
not defined by system C library headers unlike glibc where it is defined
in sys/cdefs.h and that header gets pulled in indirectly via
features.h -> sys/cdef
The MIO DMAC (Media IO DMA Controller) is used in UniPhier LD4,
Pro4, and sLD8 SoCs.
Signed-off-by: Masahiro Yamada
Reviewed-by: Rob Herring
---
Changes in v3:
- Add Rob's Reviewed-by
Changes in v2:
- Rename the node "dmac" to "dma-controller"
- Remove dma-channels property
.../devicetree
The MIO DMAC (Media IO DMA Controller) is used in UniPhier LD4,
Pro4, and sLD8 SoCs.
Signed-off-by: Masahiro Yamada
---
Changes in v3:
- Get residue from on-flight chunk
- Use GFP_NOWAIT instead of GFP_KERNEL in prep_slave_sg
- Use device_config hook
- Add NULL pointer check for txstate
Cha
1/2: DT-binding
2/2: driver
Masahiro Yamada (2):
dt-bindings: dmaengine: add DT binding for UniPhier MIO DMAC
dmaengine: uniphier-mdmac: add UniPhier MIO DMAC driver
.../devicetree/bindings/dma/uniphier-mio-dmac.txt | 25 ++
MAINTAINERS| 1 +
driv
On 09/12/2018 07:48 PM, David Lechner wrote:
This adds ratelimiting to the message that is printed when reading a
power supply property via sysfs returns an error. This will prevent
userspace applications from unintentionally dDOSing the system by
continuosuly reading a property that returns an e
On Wed, Sep 12, 2018 at 11:10 PM Arnd Bergmann wrote:
>
> The ceph_ioctl function is used both for files and directories, but only
> the files support doing that in 32-bit compat mode.
>
> For consistency, add the same compat handler to the dir operations
> as well.
>
> Cc: sta...@vger.kernel.org
This adds ratelimiting to the message that is printed when reading a
power supply property via sysfs returns an error. This will prevent
userspace applications from unintentionally dDOSing the system by
continuosuly reading a property that returns an error.
Signed-off-by: David Lechner
---
drive
On 13/09/18 01:01, Arnd Bergmann wrote:
A handful of drivers all have a trivial wrapper around their ioctl
handler, but don't call the compat_ptr() conversion function at the
moment. In practice this does not matter, since none of them are used
on the s390 architecture and for all other architect
On 9/12/18 4:40 PM, a...@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2018-09-12-16-40 has been uploaded to
>
>http://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of my -m
This series introduces a new SPI mode flag, SPI_CS_WORD, that indicates that
the chip select line should be toggled after each word sent. This series
includes examples of how this can be implemented for both an SPI controller
and an SPI device.
The motivation here is to take advantage of DMA trans
This adds a new SPI mode flag, SPI_CS_WORD, that is used to indicate
that a SPI device requires the chip select to be toggled after each
word that is transferred.
Signed-off-by: David Lechner
---
include/linux/spi/spi.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/
This adds support for the SPI_CS_WORD flag to the TI DaVinci SPI
driver. This mode can be used as long as we are using the hardware
chip select and not a GPIO chip select.
Signed-off-by: David Lechner
---
drivers/spi/spi-davinci.c | 11 ---
1 file changed, 8 insertions(+), 3 deletions(-)
This adds a default software implementation for the SPI_CS_WORD flag for
controllers that don't have such a feature.
The SPI_CS_WORD flag indicates that the CS line should be toggled
between each word sent, not just between each transfer. The
implementation works by using existing functions to spl
This changes how the SPI message for the triggered buffer is setup in
the TI ADS7950 A/DC driver. By using the SPI_CS_WORD flag, we can read
multiple samples in a single SPI transfer. If the SPI controller
supports DMA transfers, we can see a significant reduction in CPU usage.
For example, on an
> -Original Message-
> From: Jiri Kosina [mailto:ji...@kernel.org]
>
>
> @@ -325,10 +326,13 @@ static int __ptrace_may_access(struct task_struct
> *task, unsigned int mode)
> mm = task->mm;
> if (mm &&
> ((get_dumpable(mm) != SUID_DUMP_USER) &&
> - !ptrace_
On Thu, Sep 6, 2018 at 8:28 AM, Tycho Andersen wrote:
> As an alternative to SECCOMP_FILTER_FLAG_GET_LISTENER, perhaps a ptrace()
> version which can acquire filters is useful. There are at least two reasons
> this is preferable, even though it uses ptrace:
>
> 1. You can control tasks that aren't
On Sat, Sep 08, 2018 at 02:07:41PM +0200, Thomas Gleixner wrote:
> On Tue, 4 Sep 2018, Fenghua Yu wrote:
> >
> > Signed-off-by: Xiaochen Shen
> > Signed-off-by: Fenghua Yu
>
> Sigh. Am I supposed to assume that this patch is authored by Xiaochen?
Yes, Xiaochen is the author. Sorry for the mist
On Thu, Sep 6, 2018 at 8:28 AM, Tycho Andersen wrote:
> The idea here is that the userspace handler should be able to pass an fd
> back to the trapped task, for example so it can be returned from socket().
>
> I've proposed one API here, but I'm open to other options. In particular,
> this only le
From: Xiaochen Shen
In resctrl filesystem, we have some mount options to enable
L3/L2 CDP and MBA Software Controller features if platform supports them:
mount -t resctrl resctrl [-o cdp[,cdpl2][,mba_MBps]] /sys/fs/resctrl
But currently only "cdp" option can be displayed. "cdpl2" and "mba_M
The mm-of-the-moment snapshot 2018-09-12-16-40 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You wi
On Wed, Sep 12, 2018 at 03:31:06PM -0700, Jae Hyun Yoo wrote:
> >
> >I played with the code on both sides. I had to make changes in both
> >the linux kernel and in qemu to get the code to work again.
> >See attached.
> >
> >Guenter
> >
> >---
> >Linux:
> >
> >diff --git a/drivers/i2c/busses/i2c-asp
On Tue, 28 Aug 2018 13:22:53 -0400 Johannes Weiner wrote:
> There are several definitions of those functions/macros in places that
> mess with fixed-point load averages. Provide an official version.
missed blk-iolatency.c for some reason?
---
a/block/blk-iolatency.c~sched-loadavg-consolidate-
There is a race condition between ucma_close() and ucma_resolve_ip():
CPU0CPU1
ucma_resolve_ip(): ucma_close():
ctx = ucma_get_ctx(file, cmd.id);
list_for_each_entry_safe(ctx, tmp, &file->ctx_list, list) {
mutex_lock(&mut);
On 09/12/2018 09:34 PM, Jan H. Schönherr wrote:
> That said, I see a hang, too. It seems to happen, when there is a
> cpu.scheduled!=0 group that is not a direct child of the root task group.
> You seem to have "/sys/fs/cgroup/cpu/machine" as an intermediate group.
> (The case ==0 within !=0 within
On 12.09.2018 [21:34:14 +0200], Jan H. Schönherr wrote:
> On 09/12/2018 02:24 AM, Nishanth Aravamudan wrote:
> > [ I am not subscribed to LKML, please keep me CC'd on replies ]
> >
> > I tried a simple test with several VMs (in my initial test, I have 48
> > idle 1-cpu 512-mb VMs and 2 idle 2-cpu,
On Wed, Sep 12, 2018 at 09:49:41PM +0300, Baruch Siach wrote:
> I reproduced the same Oops on Clearfog Base without any taint:
>
> [1.476401] Internal error: Oops - undefined instruction: 0 [#1] SMP ARM
...
> [1.855954] Code: e2844004 e5972000 e352 0aee (e7f001f2)
That is a BUG().
Removes an unnecessary shadowed local variable (start).
Optimize test of isdigit:
- If isalpha returns true, isdigit will return false, so no need to test.
Signed-off-by: Leonardo Brás
---
scripts/asn1_compiler.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/scripts
> The /proc/pid/numa_vamaps shows mapped address ranges to numa node id
> from where the physical pages are allocated.
All these files make the problem with useless dentry and /proc/*/* inode
instantiations worse (unlike top level /proc/* files which are
tolerable).
> +address-rangenuma-n
On 09/12/2018 02:45 PM, Jiri Kosina wrote:
> On Wed, 12 Sep 2018, Tim Chen wrote:
>
>> I'm working on a patch for choosing the Spectre v2 app to app
>> mitigation option.
>>
>> Something like the following:
>>
>> enum spectre_v2_app2app_mitigation {
>> SPECTRE_V2_APP2APP_NONE,
>> S
This changes the behavior of the KASLR logic for allocating memory for the text
sections of loadable modules. It randomizes the location of each module text
section with about 17 bits of entropy in typical use. This is enabled on X86_64
only. For 32 bit, the behavior is unchanged.
It refactors exi
Create __vmalloc_node_try_addr function that tries to allocate at a specific
address and supports caller specified behavior for whether any lazy purging
happens if there is a collision.
This new function draws from the __vmalloc_node_range implementation. Attempts
to merge the two into a single al
On Fri, Jul 27, 2018 at 03:34:49PM +0530, Raju P L S S S N wrote:
> From: Lina Iyer
>
> In addition to requests that are send to the remote processor, the
> controller may allow certain data to be written to the controller for
> use in specific cases like wakeup value when entering idle states.
>
Hi,
This is V5 of the "KASLR feature to randomize each loadable module" patchset.
The purpose is to increase the randomization and also to make the modules
randomized in relation to each other instead of just the base, so that if one
module leaks the location of the others can't be inferred.
V5 i
This adds a test module in lib/, and a script in kselftest that does
benchmarking on the allocation of memory in the module space. Performance here
would have some small impact on kernel module insertions, BPF JIT insertions
and kprobes. In the case of KASLR features for the module space, this modu
Add debugfs file "modfraginfo" for providing info on module space fragmentation.
This can be used for determining if loadable module randomization is causing any
problems for extreme module loading situations, like huge numbers of modules or
extremely large modules.
Sample output when KASLR is ena
On 09/12/2018 03:27 PM, Kees Cook wrote:
On Wed, Sep 12, 2018 at 8:29 AM, Jann Horn wrote:
+linux-api, I guess
On Tue, Sep 11, 2018 at 8:39 PM Jann Horn wrote:
Restrict the ability to inspect kernel stacks of arbitrary tasks to root
in order to prevent a local attacker from exploiting racy
On Wed, Sep 12, 2018 at 04:33:56PM -0600, Lina Iyer wrote:
> On Wed, Sep 12 2018 at 16:28 -0600, Matthias Kaehlcke wrote:
> > On Fri, Jul 27, 2018 at 03:34:48PM +0530, Raju P L S S S N wrote:
> > > From: Lina Iyer
> > >
> > > The Power Domain Controller can be programmed to wakeup the RSC and
> >
On Wed, Sep 12 2018 at 16:28 -0600, Matthias Kaehlcke wrote:
On Fri, Jul 27, 2018 at 03:34:48PM +0530, Raju P L S S S N wrote:
From: Lina Iyer
The Power Domain Controller can be programmed to wakeup the RSC and
setup the resources back in the active state, before the processor is
woken up by a
On 9/12/2018 1:30 PM, Guenter Roeck wrote:
On Wed, Sep 12, 2018 at 01:10:45PM -0700, Jae Hyun Yoo wrote:
On 9/12/2018 12:58 PM, Guenter Roeck wrote:
On Wed, Sep 12, 2018 at 09:54:51AM -0700, Jae Hyun Yoo wrote:
On 9/11/2018 6:34 PM, Guenter Roeck wrote:
On Tue, Sep 11, 2018 at 04:58:44PM -070
On Fri, Jul 27, 2018 at 03:34:48PM +0530, Raju P L S S S N wrote:
> From: Lina Iyer
>
> The Power Domain Controller can be programmed to wakeup the RSC and
> setup the resources back in the active state, before the processor is
> woken up by a timer interrupt. The wakeup value from the timer hard
On Wed, Sep 12, 2018 at 8:29 AM, Jann Horn wrote:
> +linux-api, I guess
>
> On Tue, Sep 11, 2018 at 8:39 PM Jann Horn wrote:
>>
>> Restrict the ability to inspect kernel stacks of arbitrary tasks to root
>> in order to prevent a local attacker from exploiting racy stack unwinding
>> to leak kerne
On Fri, Jul 27, 2018 at 03:34:47PM +0530, Raju P L S S S N wrote:
> From: "Raju P.L.S.S.S.N"
>
> For RSCs that have sleep & wake TCS but no dedicated active TCS, wake
> TCS can be re-purposed to send active requests. Once the active requests
> are sent and response is received, the active mode co
Hi!
> On 09/11/2018 03:05 PM, Pavel Machek wrote:
> > On Tue 2018-09-11 12:08:20, Dan Murphy wrote:
> >> Remove support for the LM3697 LED device
> >> from the ti-lmu. The LM3697 will be supported
> >> via a stand alone LED driver.
> >>
> >> Signed-off-by: Dan Murphy
> >
> > I'd really like to
On Wed, 12 Sep 2018, Tim Chen wrote:
> I'm working on a patch for choosing the Spectre v2 app to app
> mitigation option.
>
> Something like the following:
>
> enum spectre_v2_app2app_mitigation {
> SPECTRE_V2_APP2APP_NONE,
> SPECTRE_V2_APP2APP_LITE,
> SPECTRE_V2_APP2APP_
syzbot has found a reproducer for the following crash on:
HEAD commit:7c1b097f27bf Add linux-next specific files for 20180912
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=117a33be40
kernel config: https://syzkaller.appspot.com/x/.config?x
On Mon, Jul 30, 2018 at 04:21:44PM -0500, Alexandru Gagniuc wrote:
> When a PCI device is gone, we don't want to send IO to it if we can
> avoid it. We expose functionality via the irq_chip structure. As
> users of that structure may not know about the underlying PCI device,
> it's our responsibili
Commit-ID: 49e73246cbe6fe0df9cae2db87f31cdc3a0b2b61
Gitweb: https://git.kernel.org/tip/49e73246cbe6fe0df9cae2db87f31cdc3a0b2b61
Author: Zubin Mithra
AuthorDate: Wed, 12 Sep 2018 09:45:10 -0700
Committer: Ingo Molnar
CommitDate: Wed, 12 Sep 2018 21:16:16 +0200
perf/x86/intel/pt: Annotat
On 09/12/2018 10:16 AM, Tom Lendacky wrote:
>
>
> On 09/11/2018 04:16 PM, Thomas Gleixner wrote:
>> On Tue, 11 Sep 2018, Tim Chen wrote:
>>> On 09/10/2018 04:46 AM, Jiri Kosina wrote:
Nah, IBPB is actuall there, sorry. So I'll add reporting of STIBP + fixup
the missing reporting of RSB
On Wed, Sep 12, 2018 at 10:29:07AM -0700, Jagdish Tirumala wrote:
> Fix the following checkpatch error:
>
> ERROR: pointer location foo * bar should be foo *bar
> FILE: drivers/watchdog/diag288_wdt.c:202
>
> Signed-off-by: Jagdish Tirumala
Reviewed-by: Guenter Roeck
> ---
> drivers/watchdog/
On Wed, Sep 12, 2018 at 07:24:48AM +0200, Greg Kroah-Hartman wrote:
> On Tue, Sep 11, 2018 at 09:58:48PM -0700, Guenter Roeck wrote:
> > On 09/11/2018 09:58 AM, Colin King wrote:
> > > From: Colin Ian King
> > >
> > > Trivial fix to spelling mistake in comment
> > >
> > > Signed-off-by: Colin Ia
* Richard Henderson wrote:
> On 09/12/2018 07:44 AM, Matthew Wilcox wrote:
> > rth wrote a patch back in 2016 that uses gcc's address space machinery
> > to improve code generation for percpu accesses. Ingo asked for some
> > minor changes to be made, but Richard didn't respond. While looking
Ville Syrjälä - 12.09.18, 19:10:
> On Tue, Sep 11, 2018 at 12:17:05PM +0200, Martin Steigerwald wrote:
> > Cc´d Intel Gfx mailing list, in case somebody there knows something:
> >
> > Cc´d Thorsten for regression tracking… forgot initially. Can also
> > open bug report at a later time but so far I
On 09/12/2018 01:42 PM, prakash.sangappa wrote:
On 05/09/2018 04:31 PM, Dave Hansen wrote:
On 05/07/2018 06:16 PM, prakash.sangappa wrote:
It will be /proc//numa_vamaps. Yes, the behavior will be
different with respect to seeking. Output will still be text and
the format will be same.
I w
Stale mentions of irq_task are left in the kerneldoc after its removal.
Remove them.
There is still one indirect mention left but commit 3c8bb90efb6e ("rtc: Fix
hrtimer deadlock") can probably be reverted now.
Reported-by: Linus Torvalds
Signed-off-by: Alexandre Belloni
---
drivers/rtc/interfa
On 05/09/2018 04:31 PM, Dave Hansen wrote:
On 05/07/2018 06:16 PM, prakash.sangappa wrote:
It will be /proc//numa_vamaps. Yes, the behavior will be
different with respect to seeking. Output will still be text and
the format will be same.
I want to get feedback on this approach.
I think it w
On Wed, Sep 12, 2018 at 5:27 AM, Oleg Nesterov wrote:
> On 09/11, Kees Cook wrote:
>>
>> Oh, I like this patch! This is much cleaner.
>
> it's pity. cause this means I will have to actually test this change and
> (worse) write the changelog ;)
Hehe. I know this pain well! :)
>> > @@ -410,11 +365
Hi!
> >>> No, we are not back to full circle.
> >>>
> >>> Or at least we should not be.
> >>>
> >>> Yes, hw_pattern can have some limitation pattern does not, but if you
> >>> take values from hw_pattern file and put them into pattern file, you
> >>> should get the same pattern (with more power be
On Wed, 12 Sep 2018, Michal Hocko wrote:
> > Saying that we really want THP isn't an all-or-nothing decision. We
> > certainly want to try hard to fault hugepages locally especially at task
> > startup when remapping our .text segment to thp, and MADV_HUGEPAGE works
> > very well for that. Re
On Wed, Sep 12, 2018 at 01:10:45PM -0700, Jae Hyun Yoo wrote:
> On 9/12/2018 12:58 PM, Guenter Roeck wrote:
> >On Wed, Sep 12, 2018 at 09:54:51AM -0700, Jae Hyun Yoo wrote:
> >>On 9/11/2018 6:34 PM, Guenter Roeck wrote:
> >>>On Tue, Sep 11, 2018 at 04:58:44PM -0700, Jae Hyun Yoo wrote:
> On 9/1
+Joe P
On Wed, Sep 12, 2018 at 10:17 AM Mauro Carvalho Chehab
wrote:
>
> Em Tue, 28 Aug 2018 10:44:33 -0500
> Rob Herring escreveu:
>
> > In preparation to remove the node name pointer from struct device_node,
> > convert printf users to use the %pOFn format specifier.
> >
> > Cc: Steve Longerbe
This patch provides process address range to numa node information
thru /proc//numa_vamaps file. For address ranges not having
any pages mapped, a '-' is printed instead of the numa node id.
Following is the sample of the file format
0040-0041 N1
0041-0047f000 N0
0047f000-0048 N2
Add support to check if numa node id matches when gathering pte stats,
to be used by later patches.
Signed-off-by: Prakash Sangappa
Reviewed-by: Steve Sistare
---
fs/proc/task_mmu.c | 44 +---
1 file changed, 37 insertions(+), 7 deletions(-)
diff --git a
Introduce supporting data structures and file operations. Later
patch will provide changes for generating file content.
Signed-off-by: Prakash Sangappa
Reviewed-by: Steve Sistare
---
fs/proc/base.c | 2 ++
fs/proc/internal.h | 1 +
fs/proc/task_mmu.c | 42 +
Permission to access /proc//numa_vamaps file should be governed by
PTRACE_READ_REALCREADS check to restrict getting specific VA range to numa
node mapping information.
Signed-off-by: Prakash Sangappa
Reviewed-by: Steve Sistare
---
fs/proc/base.c | 4 +++-
fs/proc/task_mmu.c | 2 +-
2 files
Add documentation for /proc//numa_vamaps in
Documentation/filesystems/proc.txt
Signed-off-by: Prakash Sangappa
Reviewed-by: Steve Sistare
---
Documentation/filesystems/proc.txt | 21 +
1 file changed, 21 insertions(+)
diff --git a/Documentation/filesystems/proc.txt
b/Docum
For analysis purpose it is useful to have numa node information
corresponding mapped virtual address ranges of a process. Currently,
the file /proc//numa_maps provides list of numa nodes from where pages
are allocated per VMA of a process. This is not useful if an user needs to
determine which numa
Allow lseeking to a process virtual address(VA), starting from where
the address range to numa node information can be read. The lseek offset
will be the process virtual address.
Signed-off-by: Prakash Sangappa
Reviewed-by: Steve Sistare
---
fs/proc/task_mmu.c | 23 ++-
1 fi
Ensure the non managed version of the un/registration functions is not used
anymore. No driver is using it anymore and they should not be necessary.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/class.c | 12 +---
include/linux/rtc.h | 5 -
2 files changed, 5 insertions(+), 12 de
On 09/12/2018 09:18 PM, Pavel Machek wrote:
> Hi!
>
> diff --git a/Documentation/ABI/testing/sysfs-class-led-trigger-pattern
> b/Documentation/ABI/testing/sysfs-class-led-trigger-pattern
[..]
> +What:/sys/class/leds//hw_pattern
> +Date:September 2018
>
On 9/12/2018 12:58 PM, Guenter Roeck wrote:
On Wed, Sep 12, 2018 at 09:54:51AM -0700, Jae Hyun Yoo wrote:
On 9/11/2018 6:34 PM, Guenter Roeck wrote:
On Tue, Sep 11, 2018 at 04:58:44PM -0700, Jae Hyun Yoo wrote:
On 9/11/2018 4:33 PM, Guenter Roeck wrote:
Looking into the patch, clearing the in
On Tue, 11 Sep 2018 at 12:34, Kirill A. Shutemov
wrote:
>
> A transparent huge page is represented by a single entry on an LRU list.
> Therefore, we can only make unevictable an entire compound page, not
> individual subpages.
>
> If a user tries to mlock() part of a huge page, we want the rest of
On 12/09/2018 17:08:53+0200, Arnd Bergmann wrote:
> We no longer need the rtc compat handling to be in common code, now that
> all drivers are either moved to the rtc-class framework, or (rarely)
> exist in drivers/char for architectures without compat mode (m68k,
> alpha and ia64, respectively).
>
On Wed, Sep 12, 2018 at 09:54:51AM -0700, Jae Hyun Yoo wrote:
> On 9/11/2018 6:34 PM, Guenter Roeck wrote:
> >On Tue, Sep 11, 2018 at 04:58:44PM -0700, Jae Hyun Yoo wrote:
> >>On 9/11/2018 4:33 PM, Guenter Roeck wrote:
> >>>Looking into the patch, clearing the interrupt status at the end of an
> >>
Commit-ID: cf40361ede6cf9dc09349e4c049dc0d166ca2d8b
Gitweb: https://git.kernel.org/tip/cf40361ede6cf9dc09349e4c049dc0d166ca2d8b
Author: Guenter Roeck
AuthorDate: Tue, 11 Sep 2018 11:18:12 -0700
Committer: Thomas Gleixner
CommitDate: Wed, 12 Sep 2018 21:53:34 +0200
x86/efi: Load fixmap
A perf event has many attributes that are maintained in a separate
structure that should be provided when a new perf_event is created.
In preparation for the transition to perf_events the required attribute
structures are created for all the events that may be used in the
measurements. Most attrib
From: Tony Krowiak
Notes:
=
Patches 1-2 (by David) are posted with this series because they are not
currently available in our master branch, upon which this series is based,
and because this series is dependent upon them.
This patch series works with the v8 QEMU patches.
Abstract:
=
From: David Hildenbrand
VCPU requests and VCPU blocking right now don't take care of the vSIE
(as it was not necessary until now). But we want to have synchronous VCPU
requests that will also be handled before running the vSIE again.
So let's simulate a SIE entry of the VCPU when calling the sie
This reverts commit 12eeeb4f4733bbc4481d01df35933fc15beb8b19.
The patch claims it fixes accessing memory with null pointer on
skl_interrupt() and snd_hdac_bus_update_rirb() path, but in fact it
has no effect.
There are two problems: 1) skl_init_chip() is called twice, before
and after dma buffer
From: Pierre Morel
When the guest schedules a SIE with a CRYCB FORMAT-1 CRYCB,
we are able to schedule it in the host with a FORMAT-2 CRYCB
if the host uses FORMAT-2.
Signed-off-by: Pierre Morel
Signed-off-by: Tony Krowiak
---
arch/s390/kvm/vsie.c | 33 -
1 f
Internally, skl_init_chip() calls snd_hdac_bus_init_chip() which
1) sets bus->chip_init to prevent multiple entrances before device
is stopped; 2) enables interrupt.
We shouldn't use it for the purpose of resetting device only because
1) when we really want to initialize device, we won't be able t
101 - 200 of 720 matches
Mail list logo
