On Fri, Jun 22, 2018 at 8:15 AM Rik van Riel wrote:
>
> On Fri, 2018-06-22 at 08:04 -0700, Andy Lutomirski wrote:
> > On Wed, Jun 20, 2018 at 12:57 PM Rik van Riel
> > wrote:
> > >
> > > Lazy TLB mode can result in an idle CPU being woken up by a TLB
> > > flush,
> > > when all it really needs
ISPIF hardware modules on 8x16 and 8x96 are similar. However on
8x96 the ISPIF routes data to two VFE hardware modules. Add
separate interrupt handler for 8x96 to handle the additional
interrupts.
Signed-off-by: Todor Tomov
---
drivers/media/platform/qcom/camss/camss-ispif.c | 76
Update the document to describe the support of Camera Subsystem
on MSM8996/APQ8096.
Signed-off-by: Todor Tomov
---
Documentation/media/v4l-drivers/qcom_camss.rst | 93 +++---
.../media/v4l-drivers/qcom_camss_8x96_graph.dot| 104 +
2 files changed, 164
Printing "err 0" to the user in the warning message is not particularly
useful, especially when this gets transformed into a -ENOENT for the
remainder of the call chain.
Signed-off-by: Jason A. Donenfeld
---
kernel/module.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Restructure lane configuration so it is simpler and will allow
similar (although not the same) handling for different hardware
versions.
Signed-off-by: Todor Tomov
---
.../platform/qcom/camss/camss-csiphy-2ph-1-0.c | 48 --
On Mon, Jun 18, 2018 at 12:54:29PM +, Dave Hansen wrote:
> On 06/18/2018 03:07 AM, Kirill A. Shutemov wrote:
> > On Wed, Jun 13, 2018 at 06:20:10PM +, Dave Hansen wrote:
> >>> +int page_keyid(const struct page *page)
> >>> +{
> >>> + if (mktme_status != MKTME_ENABLED)
> >>> +
On Fri 22-06-18 17:46:23, Jason A. Donenfeld wrote:
> KASAN depends on having access to some of the accounting that SLUB_DEBUG
> does; without it, there are immediate crashes [1]. So, the natural thing
> to do is to make KASAN select SLUB_DEBUG.
>
> [1]
>
Masahiro,
Am Freitag, 22. Juni 2018, 16:37:21 CEST schrieb Masahiro Yamada:
> Hi Richard,
>
>
> 2018-06-19 21:07 GMT+09:00 Richard Weinberger :
> > The denali NAND flash controller needs at least two clocks to operate,
> > nand_clk and nand_x_clk.
> > Since 1bb88666775e ("mtd: nand: denali:
On Fri, Jun 22, 2018 at 03:35:18PM +, Thomas Gleixner wrote:
> On Fri, 22 Jun 2018, Kirill A. Shutemov wrote:
> > On Fri, Jun 22, 2018 at 02:05:47PM +, Thomas Gleixner wrote:
> > > On Tue, 12 Jun 2018, Kirill A. Shutemov wrote:
> > >
> > > > __pgtable_l5_enabled shouldn't be needed after
> The other point is a quite pointless assumption that existing scrollback is
> "optimized". Even vgacon mostly uses software scrollback these days, as the
> amount of VGA display memory is really small.
All of our console driver code is horribly unoptimized for most of
todays hardware. Long ago
On Thu, 21 Jun 2018 17:07:30 -0400
William Breathitt Gray wrote:
> This patch adds high-level documentation about the Generic Counter
> interface.
>
> Signed-off-by: William Breathitt Gray
Reviewed-by: Jonathan Cameron
> ---
> Documentation/driver-api/generic-counter.rst | 342
On Fri, 2018-06-22 at 10:01 -0700, Dave Hansen wrote:
> On 06/20/2018 12:56 PM, Rik van Riel wrote:
> > +#define TLBSTATE_OK0
> > +#define TLBSTATE_LAZY 1
>
> Could we spell out a bit more about what "OK" means in comments? It
> obviously means "not lazy", but anything else?
After
Hey Akhil,
On Fri, 2018-06-22 at 12:33 +0530, Akhil P Oommen wrote:
> On 6/22/2018 6:41 AM, Ezequiel Garcia wrote:
> > Hey Enric,
> >
> > On Fri, 2018-06-22 at 00:04 +0200, Enric Balletbo i Serra wrote:
> > > When the devfreq driver and the governor driver are built as
> > > modules,
> > > the
On Wed 23 May 17:35 PDT 2018, Rishabh Bhatnagar wrote:
> LLCC (Last Level Cache Controller) provides additional cache memory
> in the system. LLCC is partitioned into multiple slices and each
> slice gets its own priority, size, ID and other config parameters.
> LLCC driver programs these
On Fri, 22 Jun 2018 11:24:38 +0100
Punit Agrawal wrote:
> Michal Hocko writes:
>
> > On Fri 22-06-18 16:58:05, Hanjun Guo wrote:
> >> On 2018/6/20 19:51, Punit Agrawal wrote:
> >> > Xie XiuQi writes:
> >> >
> >> >> Hi Lorenzo, Punit,
> >> >>
> >> >>
> >> >> On 2018/6/20 0:32, Lorenzo
On Fri, Jun 22, 2018 at 06:28:43AM -0700, Paul E. McKenney wrote:
> On Thu, Jun 21, 2018 at 10:56:59PM -0700, Joel Fernandes wrote:
> > Hi Paul,
> >
> > On Wed, Jun 20, 2018 at 09:49:02AM -0700, Paul E. McKenney wrote:
> > > On Thu, Jun 21, 2018 at 01:05:22AM +0900, Byungchul Park wrote:
> > > >
On Fri 22 Jun 10:58 PDT 2018, Bjorn Andersson wrote:
> On Mon 18 Jun 13:52 PDT 2018, Stephen Boyd wrote:
>
> > We rely on devices to use pinmuxing configurations in DT to select the
> > GPIO function (function 0) if they're going to use the gpio in GPIO
> > mode. Let's simplify things for driver
Hi Alan,
On Fri, Jun 22, 2018 at 02:09:04PM -0400, Alan Stern wrote:
> On Fri, 22 Jun 2018, Will Deacon wrote:
> > On Thu, Jun 21, 2018 at 01:27:12PM -0400, Alan Stern wrote:
> > > More than one kernel developer has expressed the opinion that the LKMM
> > > should enforce ordering of writes by
On Fri, 22 Jun 2018, Michal Hocko wrote:
> > > preempt_disable() is required because it calls kvm_kick_many_cpus() with
> > > wait == true because KVM_REQ_APIC_PAGE_RELOAD sets KVM_REQUEST_WAIT and
> > > thus the smp_call_function_many() is going to block until all cpus can
> > > run
> > >
On Thu, Jun 07, 2018 at 02:24:34PM +0200, Petr Mladek wrote:
> On Mon 2018-06-04 13:37:08, Thierry Escande wrote:
> > If the test_printf module is loaded before the crng is initialized, the
> > plain 'p' tests will fail because the printed address will not be hashed
> > and the buffer will contain
On Thu, Jun 21, 2018 at 10:32:58AM +0200, Michal Hocko wrote:
[Cc Reza Arbab - I remember he was able to hit some bugs in memblock
registration code when I was reworking that area previously]
Thanks for the heads-up!
I have verified that this patchset doesn't seem to cause any regression
in
On 2018-06-22 22:43, Ezequiel Garcia wrote:
Hey Akhil,
On Fri, 2018-06-22 at 12:33 +0530, Akhil P Oommen wrote:
On 6/22/2018 6:41 AM, Ezequiel Garcia wrote:
> Hey Enric,
>
> On Fri, 2018-06-22 at 00:04 +0200, Enric Balletbo i Serra wrote:
> > When the devfreq driver and the governor driver are
On Fri, Jun 22, 2018 at 1:19 PM Rik van Riel wrote:
>
> On Fri, 2018-06-22 at 09:01 -0700, Andy Lutomirski wrote:
> > Hmm, fair enough. I think a better heuristic would be if the
> > estimated idle duration is more than, say, 10ms. I *think* the code
> > has been cleaned up enough that this is
This code lives entirely within the RISC-V arch code. I've left it
within an "#ifdef CONFIG_EARLY_PRINTK" despite always having
EARLY_PRINTK support on RISC-V just in case someone wants to remove
it.
Signed-off-by: Palmer Dabbelt
---
arch/riscv/kernel/setup.c | 27 +++
On Fri, 22 Jun 2018 14:48:56 PDT (-0700), Daniel Lustig wrote:
On 6/22/2018 2:17 PM, Palmer Dabbelt wrote:
Dan runs the RISC-V memory model working group. I've been forwarding
him LKMM emails that end up in my inbox, but I'm far from an expert in
this stuff. He requested to be added as a
On Fri, Jun 22, 2018 at 2:13 AM Hans de Goede wrote:
>
> Hi,
>
> On 22-06-18 09:16, Benjamin Tissoires wrote:
> > On Fri, Jun 22, 2018 at 4:27 AM, Stephen Boyd wrote:
> >> Use devm here to save some lines and prepare for bulk regulator usage in
> >> this driver. Otherwise, when we devm bulk get
The user requests a pseudo-locked region by providing a schemata to a
resource group that is in the pseudo-locksetup mode. This is the
functionality that consumes the parsed user data and creates the
pseudo-locked region.
First, required information is deduced from user provided data.
This
At this time there are no constraints on how bitmasks represented by
schemata can be associated with closids represented by resource groups. A
bitmask of one class of service can without any objections overlap with the
bitmask of another class of service.
The concept of "mode" is introduced in
During CAT feature discovery the capacity bitmasks (CBMs) associated
with all the classes of service are initialized to all ones, even if the
class of service is not in use. Introduce a test that can be used to
determine if a class of service is in use. This test enables code
interested in parsing
The schemata file displays the allocations associated with each domain of
each resource. The syntax of this file reflects the capacity bitmask (CBM)
of the actual allocation. In order to determine the actual size of an
allocation the user needs to dig through three different files to query the
A new resctrl file "mode" associated with each resource group is
introduced. This file will display the resource group's current mode and an
administrator can also use it to modify the resource group's mode.
Only shareable mode is currently supported.
Signed-off-by: Reinette Chatre
The two modes used to manage Cache Pseudo-Locked regions are introduced. A
resource group is assigned "pseudo-locksetup" mode when the user indicates
that this resource group will be used for a Cache Pseudo-Locked
region. When the Cache Pseudo-Locked region has been set up successfully
after the
Each RDT resource group is associated with a mode that will reflect
the level of sharing of its allocations. The default, shareable, will be
associated with each resource group on creation since it is zero and
resource groups are created with kzalloc. The managing of the mode of a
resource group
On Fri, Jun 22, 2018 at 01:59:44PM +0200, Thomas Gleixner wrote:
> On Fri, 22 Jun 2018, Thomas Gleixner wrote:
> > The whole thing is simply:
> >
> > handle_ac()
> > {
> > if (user_mode(regs)) {
> > do_trap(AC, SIGBUS, ...);
> > } else {
> >
On Thu, Jun 21, 2018 at 01:24:34AM +, mario.limoncie...@dell.com wrote:
> > -Original Message-
> > From: Darren Hart [mailto:dvh...@infradead.org]
> > Sent: Wednesday, June 20, 2018 7:17 PM
> > To: Kees Cook
> > Cc: LKML; Andy Shevchenko; Platform Driver; Mihai Donțu; Limonciello,
On Fri, Jun 22, 2018 at 11:28:21PM +0800, Wei Xu wrote:
> On 2018/6/22 22:28, Mark Rutland wrote:
> >On Fri, Jun 22, 2018 at 09:18:27PM +0800, Wei Xu wrote:
> >> [0.227507] Mem abort info:
> >> [0.230390] ESR = 0x9606
> >> [0.233517] Exception class = DABT (current
On Fri, 22 Jun 2018, Andy Lutomirski wrote:
> On Fri, Jun 22, 2018 at 7:28 AM Thomas Gleixner wrote:
> > > +unsigned long read_task_fsbase(struct task_struct *task)
> > > +{
> > > + unsigned long fsbase;
> > > +
> > > + if (task == current) {
> > > + fsbase = read_fsbase();
>
Hi,
On Wed, Jun 06, 2018 at 04:00:42PM +0200, Greg Kroah-Hartman wrote:
> On Tue, Jun 05, 2018 at 04:53:34PM +0200, Peter Zijlstra wrote:
> > On Tue, Jun 05, 2018 at 04:43:04PM +0200, Peter Zijlstra wrote:
> >
> > > I can make a proper patch, hold on.
> >
> > ---
> > Subject: atomic/tty: Fix up
On Mon 21 May 23:23 PDT 2018, Stephen Boyd wrote:
> Add the CPU PMU on sdm845 to get perf support for hardware events.
>
> Signed-off-by: Stephen Boyd
Reviewed-by: Bjorn Andersson
Regards,
Bjorn
> ---
> arch/arm64/boot/dts/qcom/sdm845.dtsi | 5 +
> 1 file changed, 5 insertions(+)
>
>
Commit-ID: 784e0300fe9fe4aa81bd7df9d59e138f56bb605b
Gitweb: https://git.kernel.org/tip/784e0300fe9fe4aa81bd7df9d59e138f56bb605b
Author: Will Deacon
AuthorDate: Fri, 22 Jun 2018 11:45:07 +0100
Committer: Thomas Gleixner
CommitDate: Fri, 22 Jun 2018 19:04:22 +0200
rseq: Avoid infinite
On Thu, 21 Jun 2018 17:08:46 -0400
William Breathitt Gray wrote:
> From: Fabrice Gasnier
>
> Add support for new counter device to stm32-lptimer.
>
> Signed-off-by: Fabrice Gasnier
> Signed-off-by: William Breathitt Gray
Reviewed-by: Jonathan Cameron
> ---
> drivers/counter/Kconfig
On Wed 23 May 17:35 PDT 2018, Rishabh Bhatnagar wrote:
> Documentation for last level cache controller device tree bindings,
> client bindings usage examples.
>
> Signed-off-by: Channagoud Kadabi
> Signed-off-by: Rishabh Bhatnagar
> Reviewed-by: Evan Green
> Reviewed-by: Rob Herring
Current Hyper-V TLFS (v5.0b) claims that HvCallSendSyntheticClusterIpi
hypercall can't be 'fast' (passing parameters through registers) but
apparently this is not true, Windows always uses 'fast' version. We can
do the same in Linux too.
Signed-off-by: Vitaly Kuznetsov
---
GCC considers the number of statements in inlined assembly blocks,
according to new-lines and semicolons, as an indication to the cost of
the block in time and space. This data is distorted by the kernel code,
which puts information in alternative sections. As a result, the
compiler may perform
On Fri, 22 Jun 2018 at 17:23, Peter Zijlstra wrote:
>
> On Fri, Jun 22, 2018 at 01:37:13PM +0200, Peter Zijlstra wrote:
> > That is true.. So we could limit the scaling to the case where there is
> > no idle time, something like:
> >
> > util = sg_cpu->util_cfs;
> >
> > cap_cfs =
Using macros for inline assembly improves both readability and
compilation decisions that are distorted by big assembly blocks that use
alternative sections. Compile macros.S and use it to assemble all C
files. Currently, only x86 will use it.
Cc: Sam Ravnborg
Cc: Masahiro Yamada
Cc: Michal
GCC considers the number of statements in inlined assembly blocks,
according to new-lines and semicolons, as an indication to the cost of
the block in time and space. This data is distorted by the kernel code,
which puts information in alternative sections. As a result, the
compiler may perform
Use assembly macros for static_cpu_has() and call them from inline
assembly. This not only makes the code more readable, but also improves
compilation decision, specifically inline decisions which GCC base on
the number of new lines in inline assembly.
The patch slightly increases the kernel
GCC considers the number of statements in inlined assembly blocks,
according to new-lines and semicolons, as an indication to the cost of
the block in time and space. This data is distorted by the kernel code,
which puts information in alternative sections. As a result, the
compiler may perform
2018-06-09 6:47 GMT+09:00 Greg Thelen :
> Non gcc-5 builds with CONFIG_STACK_VALIDATION=y and
> SKIP_STACK_VALIDATION=1 fail.
> Example output:
> /bin/sh: init/.tmp_main.o: Permission denied
>
> commit 96f60dfa5819 ("trace: Use -mcount-record for dynamic ftrace"),
> added a mismatched endif.
On Fri, Jun 22, 2018 at 06:50:56PM +0200, Thomas Gleixner wrote:
> > The magic, which I cut out, will rewrite the "jmp 6f, nops" thing to
> > "jmp %l[y_{yes,no}]" at the alternative patching and we'll loose the
> > dynamic test, pinning the condition forever more.
>
> Hrm. Memory seems have to
Hi Shammer,
On Fri, 22 Jun 2018 17:31:40 +0100,
Shameerali Kolothum Thodi wrote:
>
> Hi Marc,
>
> > -Original Message-
> > From: Marc Zyngier [mailto:marc.zyng...@arm.com]
> > Sent: 20 June 2018 14:53
> > To: linux-kernel@vger.kernel.org
> > Cc: Thomas Gleixner ; Ard Biesheuvel
> > ;
On Mon 18 Jun 13:52 PDT 2018, Stephen Boyd wrote:
> We rely on devices to use pinmuxing configurations in DT to select the
> GPIO function (function 0) if they're going to use the gpio in GPIO
> mode. Let's simplify things for driver authors by implementing
> gpio_request_enable() for this
Smack: Mark inode instant in smack_task_to_inode
/proc clean-up in commit 1bbc55131e59bd099fdc568d3aa0b42634dbd188
resulted in smack_task_to_inode() being called before smack_d_instantiate.
This resulted in the smk_inode value being ignored, even while present
for files in /proc/self. Marking the
On Fri, 22 Jun 2018, Will Deacon wrote:
> Hi Alan,
>
> On Fri, Jun 22, 2018 at 02:09:04PM -0400, Alan Stern wrote:
> > On Fri, 22 Jun 2018, Will Deacon wrote:
> > > On Thu, Jun 21, 2018 at 01:27:12PM -0400, Alan Stern wrote:
> > > > More than one kernel developer has expressed the opinion that
On 06/22/18 19:28, Joe Perches wrote:
On Fri, 2018-06-22 at 14:48 +0200, Michael Straube wrote:
On 06/22/18 12:57, Dan Carpenter wrote:
On Fri, Jun 22, 2018 at 03:54:22AM -0700, Joe Perches wrote:
On Fri, 2018-06-22 at 13:40 +0300, Dan Carpenter wrote:
On Thu, Jun 21, 2018 at 08:22:30PM
On 06/15/2018 05:04 AM, Chunyan Zhang wrote:
> Host Driver Version 4.10 adds a new bit in Host Control 2 Register
> for selecting Auto CMD23 or Auto CMD12 for ADMA3 data transfer.
We don't support ADMA3. It would require changes to the block driver.
So is this change needed?
>
> Signed-off-by:
On Fri, Jun 22, 2018 at 11:19:16AM -0700, Joel Fernandes wrote:
> On Fri, Jun 22, 2018 at 06:28:43AM -0700, Paul E. McKenney wrote:
> > On Thu, Jun 21, 2018 at 10:56:59PM -0700, Joel Fernandes wrote:
> > > Hi Paul,
> > >
> > > On Wed, Jun 20, 2018 at 09:49:02AM -0700, Paul E. McKenney wrote:
> >
On Fri, Jun 22, 2018 at 11:42:46AM -0700, Guenter Roeck wrote:
> Hi,
>
> a few days ago, m68k boot tests in linux-next started to crash.
> I bisected the problem to commit 'xarray: Replace exceptional entries'.
> Bisect and crash logs are attached below.
Thank you! I was afraid something like
Commit 26f09e9b3a06 ("mm/memblock: add memblock memory allocation apis")
introduced two new function definitions:
memblock_virt_alloc_try_nid_nopanic()
memblock_virt_alloc_try_nid()
Commit ea1f5f3712af ("mm: define memblock_virt_alloc_try_nid_raw")
introduced the following function
On Fri, Jun 22, 2018 at 04:45:47PM -0400, Stefan Berger wrote:
> On 06/22/2018 04:43 PM, Jason Gunthorpe wrote:
> >On Fri, Jun 22, 2018 at 12:46:11PM -0400, Stefan Berger wrote:
> >>Implement tpm_chip_find() for other subsystems to find a TPM chip and
> >>get a reference to that chip.
> >>
>
On Fri, Jun 22, 2018 at 05:00:42PM -0400, Steven Rostedt wrote:
> On Fri, 22 Jun 2018 13:58:13 -0700
> "Paul E. McKenney" wrote:
>
> > Something like this:
> >
> > IRQ entered
> >
> > And never exited. Ever. I actually saw this in 2011.
>
> I still believe this was actually a bug. And
On Sat, Jun 23, 2018 at 04:03:11AM +0800, Yang Shi wrote:
> When merging anonymous page vma, if the size of vma can fit in at least
> one hugepage, the mm will be registered for khugepaged for collapsing
> THP in the future.
>
> But, it skips shmem vma. Doing so for shmem too, but not
The user can request entering pseudo-locksetup mode by writing
"pseudo-locksetup" to the mode file. Act on this request as well as
support switching from a pseudo-locksetup mode (before pseudo-locked
mode was entered). It is not supported to modify the mode once
pseudo-locked mode has been
By default, if the opener has CAP_DAC_OVERRIDE, a kernfs file can be opened
regardless of RW permissions. Writing to a kernfs file will thus succeed
even if permissions are .
It's required to restrict the actions that can be performed on a resource
group from userspace based on the mode of
The user triggers the creation of a pseudo-locked region when writing a
valid schemata to the schemata file of a resource group in the
pseudo-locksetup mode.
A valid schemata is one that: (1) does not overlap with any other resource
group, (2) does not involve a cache that already contains a
Information about resources as well as resource groups are contained in a
variety of resctrl files. Now that pseudo-locked regions can be created the
files can be updated to present appropriate information to the user.
Update the resource group's schemata file to show only the information of
the
Currently when a new resource group is created its allocations would be
those that belonged to the resource group to which its closid belonged
previously.
That is, we can encounter a case like:
mkdir newgroup
cat newgroup/schemata
L2:0=ff;1=ff
echo 'L2:0=0xf0;1=0xf0' > newgroup/schemata
cat
When a resource group is used for Cache Pseudo-Locking then the region of
cache ends up being orphaned with no class of service referring to it. The
resctrl files intended to manage how the classes of services are utilized
thus become irrelevant.
The fact that a resctrl file is not relevant can
Add description of Cache Pseudo-Locking feature, its interface, as well as
an example of its usage.
Signed-off-by: Reinette Chatre
Signed-off-by: Thomas Gleixner
Cc: fenghua...@intel.com
Cc: tony.l...@intel.com
Cc: vikas.shiva...@linux.intel.com
Cc: gavin.hind...@intel.com
Cc:
Michael,
On Mon, 4 Jun 2018, Michael Rodin wrote:
> The variable "vclocks_used" doesn't appear to be "read mostly".
> Measurements of the access frequency with perf stat [1] and
> perf report show, that approximately half of the accesses to
> this variable are write accesses and happen in
The locksetup mode is the way in which the user communicates that the
resource group will be used for a pseudo-locked region. Locksetup mode
should thus ensure that all restrictions on a resource group are met before
locksetup mode can be entered. The resource group should also be configured
to
A pseudo-locked region is introduced representing an instance of a
pseudo-locked cache region. Each cache instance (domain) can support one
pseudo-locked region. Similarly a resource group can be used for one
pseudo-locked region.
Include a pointer to a pseudo-locked region from the domain and
Resource groups used for pseudo-locking do not require the same work on
removal as the other resource groups.
The resource group removal is split in two in preparation for support of
pseudo-locking resource groups. A single re-ordering occurs - the
setting of the rdtgrp flag is moved to later.
This file has never existed in the upstream kernel, but it's guarded by
an #ifdef that's also never existed in the upstream kernel. As a part
of our interrupt controller refactoring this header is no longer
necessary, but this reference managed to sneak in anyway.
Signed-off-by: Palmer Dabbelt
The RISC-V ISA mandantes the presence of a simple, per-hart (hardware
thread) interrupt controller availiable to supervisor mode. This patch
set adds a driver for this interrupt controller.
The patch set itself has been around in various flavors for a while, but
as far as I remember it's never
From: Palmer Dabbelt
This patch adds documentation on the RISC-V local interrupt controller,
which is a per-hart interrupt controller that manages all interrupts
entering a RISC-V hart. This interrupt controller is present on all
RISC-V systems.
Signed-off-by: Palmer Dabbelt
---
On Fri, Jun 22, 2018 at 10:59:17AM +0200, Takashi Iwai wrote:
> The commit 5d9f40b56630 ("platform/x86: ideapad-laptop: Add
> Y520-15IKBN to no_hw_rfkill") added the entry for Y20-15IKBN, and it
> turned out that another variant, Y20-15IKBM, also requires the
> no_hw_rfkill.
>
> Trim the last
On Fri, 2018-06-22 at 09:01 -0700, Andy Lutomirski wrote:
> Hmm, fair enough. I think a better heuristic would be if the
> estimated idle duration is more than, say, 10ms. I *think* the code
> has been cleaned up enough that this is easy now. (Using time
> instead
> of C6 will make it a lot
On Fri, Jun 22, 2018 at 12:46:10PM -0400, Stefan Berger wrote:
> Rename tpm_chip_find_get() to tpm_get_ops(). This now matches
> the name of its counter part tpm_put_ops() better.
>
> Signed-off-by: Stefan Berger
> drivers/char/tpm/tpm-chip.c | 4 ++--
> drivers/char/tpm/tpm-interface.c |
On 06/22/2018 04:43 PM, Jason Gunthorpe wrote:
On Fri, Jun 22, 2018 at 12:46:11PM -0400, Stefan Berger wrote:
Implement tpm_chip_find() for other subsystems to find a TPM chip and
get a reference to that chip.
Signed-off-by: Stefan Berger
drivers/char/tpm/tpm-chip.c | 27
On Mon, 4 Jun 2018, Miroslav Lichvar wrote:
> When the NTP frequency is set directly from userspace using the
> ADJ_FREQUENCY or ADJ_TICK timex mode, immediately update the
> timekeeper's multiplier instead of waiting for the next tick.
>
> This removes a hidden non-deterministic delay in
Dan runs the RISC-V memory model working group. I've been forwarding
him LKMM emails that end up in my inbox, but I'm far from an expert in
this stuff. He requested to be added as a reviewer, which seem sane to
me as it'll take a human out of the loop.
CC: Daniel Lustig
Signed-off-by: Palmer
On Wed, 30 May 2018, Mukesh Ojha wrote:
> Currently, for both non-stop clocksource and persistent clock
> there is a corner case, when a driver failed to go suspend mode.
> rtc_resume() injects the sleeptime as timekeeping_rtc_skipresume()
> returned 'false'(sleeptime_injected=false) due to which
On Fri, 22 Jun 2018, John Stultz wrote:
> On Fri, Jun 22, 2018 at 2:09 PM, Thomas Gleixner wrote:
> > On Mon, 4 Jun 2018, Miroslav Lichvar wrote:
> >
> >> When the NTP frequency is set directly from userspace using the
> >> ADJ_FREQUENCY or ADJ_TICK timex mode, immediately update the
> >>
On 6/22/2018 2:17 PM, Palmer Dabbelt wrote:
> Dan runs the RISC-V memory model working group. I've been forwarding
> him LKMM emails that end up in my inbox, but I'm far from an expert in
> this stuff. He requested to be added as a reviewer, which seem sane to
> me as it'll take a human out of
On Fri, Jun 22, 2018 at 11:09 AM, Andy Lutomirski wrote:
> One possible extra issue: IIRC /proc/.../mem uses FOLL_FORCE, which is not
> what we want here.
>
> How about just adding an explicit “read/write the seccomp-trapped task’s
> memory” primitive? That should be easier than a “open mem
On Fri, Jun 22, 2018 at 2:14 PM Paul E. McKenney
wrote:
>
> On Fri, Jun 22, 2018 at 05:00:42PM -0400, Steven Rostedt wrote:
> > On Fri, 22 Jun 2018 13:58:13 -0700
> > "Paul E. McKenney" wrote:
> >
> > > Something like this:
> > >
> > > IRQ entered
> > >
> > > And never exited. Ever. I
On Fri, Jun 22, 2018 at 11:02 AM Bae, Chang Seok
wrote:
>
> > Still setup_cpu_number() sucks.
>
> How about setup_cpu_and_node_number()?
setup_fast_cpu_node_nr()? setup_cpunr_regs()? I don't have any
brilliant ideas. Thomas?
On Fri, Jun 22, 2018 at 11:51 PM Kees Cook wrote:
>
> On Fri, Jun 22, 2018 at 11:09 AM, Andy Lutomirski wrote:
> > One possible extra issue: IIRC /proc/.../mem uses FOLL_FORCE, which is not
> > what we want here.
Uuugh, I forgot about that.
> > How about just adding an explicit “read/write
Stephen Rothwell reported that the Cache Pseudo-Locking enabling and the
kernfs support for mounting with fs_context are conflicting.
In preparation for a conflict-free merge between the two repos some
no-op hooks are created within the RDT mount function being changed by
the two features. The
The RDT system's initialization does not have the corresponding exit
handling to ensure everything initialized on load is cleaned up also.
Introduce the cleanup routines that complement all initialization. This
includes the removal of a duplicate rdtgroup_init() declaration.
Signed-off-by:
Deeper C-states impact cache content through shrinking of the cache or
flushing entire cache to memory before reducing power to the cache.
Deeper C-states will thus negatively impact the pseudo-locked regions.
To avoid impacting pseudo-locked regions C-states are limited on
pseudo-locked region
On Fri, Jun 22, 2018 at 01:59:44PM +0200, Thomas Gleixner wrote:
> On Fri, 22 Jun 2018, Thomas Gleixner wrote:
> > The whole thing is simply:
> >
> > handle_ac()
> > {
> > if (user_mode(regs)) {
> > do_trap(AC, SIGBUS, ...);
> > } else {
> >
In support of the work done to enable resource groups to have different
modes some static functions need to be available for sharing amongst
all RDT components.
Signed-off-by: Reinette Chatre
Signed-off-by: Thomas Gleixner
Cc: fenghua...@intel.com
Cc: tony.l...@intel.com
Cc:
Dear Maintainers,
The Cache Pseudo-Locking enabling series that was recently merged to the
x86/cache branch of tip was found to conflict with the new kernfs support
for mounting with fs_context.
In preparation for a conflict-free merge between the two repos some no-op
hooks are created within
In support of Cache Pseudo-Locking we need to restrict access to specific
resctrl files to protect the state of a resource group used for
pseudo-locking from being changed in unsupported ways.
Introduce two utilities that can be used to either restrict or restore the
access to all files
Each resource is associated with a configurable callback that should be
used to parse the information provided for the particular resource from
user space. In addition to the resource and domain pointers this callback
is provided with just the character buffer being parsed.
In support of flexible
At the moment all allocations are shareable. There is no way for a user to
designate that an allocation associated with a resource group cannot be
shared by another.
Introduce the new mode "exclusive". When a resource group is marked as such
it implies that no overlap is allowed between its
With cache regions now explicitly marked as "shareable" or "exclusive"
we would like to communicate to the user how portions of the cache
are used.
Introduce "bit_usage" that indicates for each resource
how portions of the cache are configured to be used.
To assist the user to distinguish
1 - 100 of 1351 matches
Mail list logo
