The SEV_FACTORY_RESET command can be used by the platform owner to
reset the non-volatile SEV related data. The command is defined in
SEV spec section 5.4
Cc: Paolo Bonzini
Cc: "Radim Krčmář"
Cc: Borislav Petkov
Cc: Herbert Xu
Cc: Gary Hook
Cc: Tom Lendacky
Cc: linux-cry...@vger.kernel.org
C
On 12/02/2017 11:26 AM, Arvind Yadav wrote:
> The change is to call free_netdev(), If of_match_node() will fail.
>
> Signed-off-by: Arvind Yadav
> ---
> drivers/net/ethernet/broadcom/genet/bcmgenet.c | 6 --
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ethe
The Platform Security Processor (PSP) is part of the AMD Secure
Processor (AMD-SP) functionality. The PSP is a dedicated processor
that provides support for key management commands in Secure Encrypted
Virtualization (SEV) mode, along with software-based Trusted Execution
Environment (TEE) to enable
The SEV_PDH_GEN command is used to re-generate the Platform
Diffie-Hellman (PDH) key. The command is defined in SEV spec section
5.6.
Cc: Paolo Bonzini
Cc: "Radim Krčmář"
Cc: Borislav Petkov
Cc: Herbert Xu
Cc: Gary Hook
Cc: Tom Lendacky
Cc: linux-cry...@vger.kernel.org
Cc: k...@vger.kernel.o
The SEV_PEK_CERT_IMPORT command can be used to import the signed PEK
certificate. The command is defined in SEV spec section 5.8.
Cc: Paolo Bonzini
Cc: "Radim Krčmář"
Cc: Borislav Petkov
Cc: Herbert Xu
Cc: Gary Hook
Cc: Tom Lendacky
Cc: linux-cry...@vger.kernel.org
Cc: k...@vger.kernel.org
C
Add a include file which defines the ioctl and command id used for
issuing SEV platform management specific commands.
Cc: Paolo Bonzini
Cc: "Radim Krčmář"
Cc: Borislav Petkov
Cc: Herbert Xu
Cc: Gary Hook
Cc: Tom Lendacky
Cc: linux-cry...@vger.kernel.org
Cc: k...@vger.kernel.org
Cc: linux-ker
The SEV_PEK_CSR command can be used to generate a PEK certificate
signing request. The command is defined in SEV spec section 5.7.
Cc: Paolo Bonzini
Cc: "Radim Krčmář"
Cc: Borislav Petkov
Cc: Herbert Xu
Cc: Gary Hook
Cc: Tom Lendacky
Cc: linux-cry...@vger.kernel.org
Cc: k...@vger.kernel.org
The SEV_PEK_GEN command is used to generate a new Platform Endorsement
Key (PEK). The command is defined in SEV spec section 5.6.
Cc: Paolo Bonzini
Cc: "Radim Krčmář"
Cc: Borislav Petkov
Cc: Herbert Xu
Cc: Gary Hook
Cc: Tom Lendacky
Cc: linux-cry...@vger.kernel.org
Cc: k...@vger.kernel.org
C
The SEV_PDH_CERT_EXPORT command can be used to export the PDH and its
certificate chain. The command is defined in SEV spec section 5.10.
Cc: Paolo Bonzini
Cc: "Radim Krčmář"
Cc: Borislav Petkov
Cc: Herbert Xu
Cc: Gary Hook
Cc: Tom Lendacky
Cc: linux-cry...@vger.kernel.org
Cc: k...@vger.kern
The config option can be used to enable SEV support on AMD Processors.
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: "H. Peter Anvin"
Cc: Paolo Bonzini
Cc: "Radim Krčmář"
Cc: Joerg Roedel
Cc: Borislav Petkov
Cc: Tom Lendacky
Cc: x...@kernel.org
Cc: k...@vger.kernel.org
Cc: linux-kernel@vger.kern
The module parameter can be used to control the SEV feature support.
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: "H. Peter Anvin"
Cc: Paolo Bonzini
Cc: "Radim Krčmář"
Cc: Joerg Roedel
Cc: Borislav Petkov
Cc: Tom Lendacky
Cc: x...@kernel.org
Cc: k...@vger.kernel.org
Cc: linux-kernel@vger.kernel
Define Secure Encrypted Virtualization (SEV) key management command id
and structure. The command definition is available in SEV KM spec
0.14 (http://support.amd.com/TechDocs/55766_SEV-KM API_Specification.pdf)
and Documentation/virtual/kvm/amd-memory-encryption.txt.
Cc: Thomas Gleixner
Cc: Ingo
The command initializes the SEV platform context and allocates a new ASID
for this guest from the SEV ASID pool. The firmware must be initialized
before we issue any guest launch commands to create a new memory encryption
context.
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: "H. Peter Anvin"
Cc: Pao
From: Borislav Petkov
This is AMD-specific hardware so present it in Kconfig only when AMD
CPU support is enabled or on ARM64 where it is also used.
Signed-off-by: Borislav Petkov
Signed-off-by: Brijesh Singh
Reviewed-by: Gary R Hook
Cc: Brijesh Singh
Cc: Tom Lendacky
Cc: Gary Hook
Cc: Her
The KVM_SEV_LAUNCH_START command is used to create a memory encryption
context within the SEV firmware. In order to do so, the guest owner
should provide the guest's policy, its public Diffie-Hellman (PDH) key
and session information. The command implements the LAUNCH_START flow
defined in SEV spec
The command is used for encrypting the guest memory region using the VM
encryption key (VEK) created during KVM_SEV_LAUNCH_START.
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: "H. Peter Anvin"
Cc: Paolo Bonzini
Cc: "Radim Krčmář"
Cc: Joerg Roedel
Cc: Borislav Petkov
Cc: Tom Lendacky
Cc: x...@ker
SEV hardware uses ASIDs to associate a memory encryption key with a
guest VM. During guest creation, a SEV VM uses the SEV_CMD_ACTIVATE
command to bind a particular ASID to the guest. Lets make sure that the
VMCB is programmed with the bound ASID before a VMRUN.
Cc: Thomas Gleixner
Cc: Ingo Molna
If hardware supports memory encryption then KVM_MEMORY_ENCRYPT_REG_REGION
and KVM_MEMORY_ENCRYPT_UNREG_REGION ioctl's can be used by userspace to
register/unregister the guest memory regions which may contain the encrypted
data (e.g guest RAM, PCI BAR, SMRAM etc).
Cc: Thomas Gleixner
Cc: Ingo Mol
The command is used for querying the SEV guest information.
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: "H. Peter Anvin"
Cc: Paolo Bonzini
Cc: "Radim Krčmář"
Cc: Joerg Roedel
Cc: Borislav Petkov
Cc: Tom Lendacky
Cc: x...@kernel.org
Cc: k...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Sign
The command is used to retrieve the measurement of contents encrypted
through the KVM_SEV_LAUNCH_UPDATE_DATA command.
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: "H. Peter Anvin"
Cc: Paolo Bonzini
Cc: "Radim Krčmář"
Cc: Joerg Roedel
Cc: Borislav Petkov
Cc: Tom Lendacky
Cc: x...@kernel.org
Cc:
The command is used for decrypting a guest memory region for debug
purposes.
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: "H. Peter Anvin"
Cc: Paolo Bonzini
Cc: "Radim Krčmář"
Cc: Joerg Roedel
Cc: Borislav Petkov
Cc: Tom Lendacky
Cc: x...@kernel.org
Cc: k...@vger.kernel.org
Cc: linux-kernel@vge
The command copies a plaintext into guest memory and encrypts it using
the VM encryption key. The command will be used for debug purposes
(e.g setting breakpoints through gdbserver)
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: "H. Peter Anvin"
Cc: Paolo Bonzini
Cc: "Radim Krčmář"
Cc: Joerg Roedel
The command is used for injecting a secret into the guest memory region.
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: "H. Peter Anvin"
Cc: Paolo Bonzini
Cc: "Radim Krčmář"
Cc: Joerg Roedel
Cc: Borislav Petkov
Cc: Tom Lendacky
Cc: x...@kernel.org
Cc: k...@vger.kernel.org
Cc: linux-kernel@vger.ke
The SEV memory encryption engine uses a tweak such that two identical
plaintext pages at different location will have different ciphertext.
So swapping or moving ciphertext of two pages will not result in
plaintext being swapped. Relocating (or migrating) physical backing
pages for a SEV guest will
On AMD platforms, under certain conditions insn_len may be zero on #NPF.
This can happen if a guest gets a page-fault on data access but the HW
table walker is not able to read the instruction page (e.g instruction
page is not present in memory).
Typically, when insn_len is zero, x86_emulate_instr
On #UD, x86_emulate_instruction() fetches the data from guest memory and
decodes the instruction bytes to assist further. When SEV is enabled, the
instruction bytes will be encrypted using the guest-specific key and the
hypervisor will no longer able to fetch the instruction bytes to assist
UD hand
The command is used for finializing the SEV guest launch process.
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: "H. Peter Anvin"
Cc: Paolo Bonzini
Cc: "Radim Krčmář"
Cc: Joerg Roedel
Cc: Borislav Petkov
Cc: Tom Lendacky
Cc: x...@kernel.org
Cc: k...@vger.kernel.org
Cc: linux-kernel@vger.kernel.or
When SEV is active, on #VMEXIT the page fault address will contain the
C-bit. We must clear the C-bit before handling the fault.
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: "H. Peter Anvin"
Cc: Paolo Bonzini
Cc: "Radim Krčmář"
Cc: Joerg Roedel
Cc: Borislav Petkov
Cc: Tom Lendacky
Cc: x...@ker
Define Secure Encrypted Virtualization (SEV) key management command id
and structure. The command definition is available in SEV KM spec
0.14 (http://support.amd.com/TechDocs/55766_SEV-KM API_Specification.pdf)
Cc: Paolo Bonzini
Cc: "Radim Krčmář"
Cc: Borislav Petkov
Cc: Herbert Xu
Cc: Gary Ho
If the hardware supports memory encryption then the
KVM_MEMORY_ENCRYPT_OP ioctl can be used by qemu to issue a platform
specific memory encryption commands.
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: "H. Peter Anvin"
Cc: Paolo Bonzini
Cc: "Radim Krčmář"
Cc: Joerg Roedel
Cc: Borislav Petkov
Cc:
A SEV-enabled guest must use ASIDs from the defined subset, while non-SEV
guests can use the remaining ASID range. The range of allowed SEV guest
ASIDs is [1 - CPUID_8000_001F[ECX][31:0]].
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: "H. Peter Anvin"
Cc: Paolo Bonzini
Cc: "Radim Krčmář"
Cc: Joerg
From: Tom Lendacky
Currently the nested_ctl variable in the vmcb_control_area structure is
used to indicate nested paging support. The nested paging support field
is actually defined as bit 0 of the field. In order to support a new
feature flag the usage of the nested_ctl and nested paging suppor
From: Tom Lendacky
Update the CPU features to include identifying and reporting on the
Secure Encrypted Virtualization (SEV) feature. SEV is identified by
CPUID 0x801f, but requires BIOS support to enable it (set bit 23 of
MSR_K8_SYSCFG and set bit 0 of MSR_K7_HWCR). Only show the SEV featu
Create a Documentation entry to describe the AMD Secure Encrypted
Virtualization (SEV) feature.
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: "H. Peter Anvin"
Cc: Paolo Bonzini
Cc: "Radim Krčmář"
Cc: Jonathan Corbet
Cc: Borislav Petkov
Cc: Tom Lendacky
Cc: k...@vger.kernel.org
Cc: x...@kernel.or
On 12/04/2017 09:48 AM, Arvind Yadav wrote:
> The platform_get_irq() function returns negative number if an error occurs,
> Zero if No irq is found and positive number if irq gets successful.
> platform_get_irq() error checking only for zero is not correct.
>
> Signed-off-by: Arvind Yadav
> ---
>
+CC Greg-KH
+CC Thomas Gleixner
2017-12-05 3:20 GMT+09:00 Mark Brown :
> On Wed, Nov 22, 2017 at 08:43:17PM +0900, Katsuhiro Suzuki wrote:
>
>> +++ b/sound/soc/uniphier/evea.c
>> @@ -0,0 +1,567 @@
>> +// SPDX-License-Identifier: GPL-2.0
>> +/*
>> + * Socionext UniPhier EVEA ADC/DAC codec driver.
>
Hi Arnd,
On Tuesday, 5 December 2017 02:37:27 EET Laurent Pinchart wrote:
> On Monday, 27 November 2017 15:19:54 EET Arnd Bergmann wrote:
> > uvc_video_get_ts() returns a 'struct timespec', but all its users
> > really want a nanoseconds variable anyway.
> >
> > Changing the deprecated ktime_get_
2017-12-05 8:28 GMT+08:00 Jim Mattson :
> That seems like a convoluted path to produce an illegal RFLAGS value.
> What's to prevent syzkaller from simply clearing bit 1 of RFLAGS with
> the KVM_SET_REGS ioctl?
Yeah, it can happen. Which do you prefer, ioctl fails or |
X86_EFLAGS_FIXED unconditiona
From: Bjorn Helgaas
Set resource structs inserted by __reserve_region_with_split() to have the
correct type. Setting the type doesn't fix any functional problem but
makes %pR on the resource work better.
Signed-off-by: Bjorn Helgaas
---
kernel/resource.c |5 +++--
1 file changed, 3 insert
Hi Arnd,
Thank you for the patch.
I'll try to review this without too much delay. In the meantime, I'm CC'ing
Sakari Ailus who might be faster than me :-)
On Monday, 27 November 2017 15:19:57 EET Arnd Bergmann wrote:
> C libraries with 64-bit time_t use an incompatible format for
> struct omap3
From: Bjorn Helgaas
Set I/O port resource structs to have IORESOURCE_IO in their type field.
Previously we marked these as merely IORESOURCE_BUSY without indicating the
type. Setting the type doesn't fix any functional problem but makes %pR
on the resource work better.
Signed-off-by: Bjorn Hel
From: Bjorn Helgaas
When we reserve regions because the user specified a "reserve=" parameter,
set the resource type to either IORESOURCE_IO (for regions below 0x1)
or IORESOURCE_MEM. The test for 0x1 is just a heuristic; obviously
there can be memory below 0x1 as well.
Improve docu
From: Bjorn Helgaas
Set I/O port resource structs to have IORESOURCE_IO in their type field.
Previously we marked these as merely IORESOURCE_BUSY without indicating the
type. Setting the type doesn't fix any functional problem but makes %pR
on the resource work better.
Signed-off-by: Bjorn Hel
From: Bjorn Helgaas
Set I/O port resource structs to have IORESOURCE_IO in their type field.
Previously we marked these as merely IORESOURCE_BUSY without indicating the
type. Setting the type doesn't fix any functional problem but makes %pR
on the resource work better.
Signed-off-by: Bjorn Hel
From: Bjorn Helgaas
Set the resource type when we reserve VGA-related I/O port resources.
The resource code doesn't actually look at the type, so it inserts
resources without a type in the tree correctly even without this change.
But if we ever print a resource without a type, it looks like this
Hi Arnd,
Thank you for the patch.
On Monday, 27 November 2017 15:19:53 EET Arnd Bergmann wrote:
> 'struct timespec' works fine here, but we try to migrate
> away from it in favor of ktime_t or timespec64. In this
> case, using ktime_t produces the simplest code.
>
> Signed-off-by: Arnd Bergmann
We have several places that insert struct resources into the iomem_resource
or ioport_resource trees without setting the type. This *works* fine
because it's obvious that a resource must be the same type as its parent,
but it does mean that if we ever print the resource with %pR, it doesn't
print
Hi Arnd,
Thank you for the patch.
On Monday, 27 November 2017 15:19:54 EET Arnd Bergmann wrote:
> uvc_video_get_ts() returns a 'struct timespec', but all its users
> really want a nanoseconds variable anyway.
>
> Changing the deprecated ktime_get_ts/ktime_get_real_ts to ktime_get
> and ktime_get
That seems like a convoluted path to produce an illegal RFLAGS value.
What's to prevent syzkaller from simply clearing bit 1 of RFLAGS with
the KVM_SET_REGS ioctl?
On Mon, Nov 20, 2017 at 4:34 PM, Wanpeng Li wrote:
> 2017-11-21 7:09 GMT+08:00 Paolo Bonzini :
>> On 20/11/2017 23:52, Wanpeng Li wro
On Monday, December 4, 2017 11:41:06 PM CET Rafael J. Wysocki wrote:
> On Monday, December 4, 2017 11:38:54 PM CET Thomas Gleixner wrote:
> > On Mon, 4 Dec 2017, Linus Torvalds wrote:
> >
> > > On Mon, Dec 4, 2017 at 2:25 PM, Rafael J. Wysocki
> > > wrote:
> > > >
> > > > So far, resume from sus
On 12/05/2017 12:06 AM, Claudiu Manoil wrote:
-Original Message-
From: Zumeng Chen [mailto:zumeng.c...@gmail.com]
Sent: Monday, December 04, 2017 5:22 AM
To: net...@vger.kernel.org; linux-kernel@vger.kernel.org
Cc: Claudiu Manoil ; da...@davemloft.net
Subject: [PATCH 1/1] gianfar: fix a f
On Mon, Dec 4, 2017 at 4:31 AM, Jason Wang wrote:
> This patch introduces an eBPF based queue selection method. With this,
> the policy could be offloaded to userspace completely through a new
> ioctl TUNSETSTEERINGEBPF.
>
> Signed-off-by: Jason Wang
> ---
> +static u16 tun_ebpf_select_queue(str
On Mon, Dec 04, 2017 at 04:51:04PM +, Wang Nan wrote:
> Simplify patch 1/3 following Namhyung's suggestion.
>
> Context adjustment for patch 2 and 3.
>
> Wang Nan (3):
> perf mmap: Fix perf backward recording
> perf tools: Don't discard prev in backward mode
> perf tools: Replace 'backw
On 11/30/2017 08:39 AM, Will Deacon wrote:
Hi again,
This is version two of the patches previously posted here:
http://lists.infradead.org/pipermail/linux-arm-kernel/2017-November/542751.html
Changes since v1 include:
* Based on v4.15-rc1
* Trampoline moved into FIXMAP area
* Exp
On 04.12.2017 23:10, rwar...@gmx.de wrote:
Hallo
someone and I got an regression with e1000e since kernel 4.14.3 and it seems
there is 4.14.4 on the way without a fix.
bug report is here:
https://bugzilla.kernel.org/show_bug.cgi?id=198047
( added stable and netdev to CC )
Yes I have a bo
On Mon, Dec 04, 2017 at 04:59:24PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.4 release.
> There are 95 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
On Mon, Dec 04, 2017 at 04:59:40PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.67 release.
> There are 38 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
On Mon, Dec 04, 2017 at 04:59:25PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.104 release.
> There are 27 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know
On Mon, Dec 04, 2017 at 04:59:14PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.18.86 release.
> There are 12 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know
On Mon, Dec 04, 2017 at 01:51:42PM -0800, Kees Cook wrote:
> On Mon, Dec 4, 2017 at 1:44 PM, Tobin C. Harding wrote:
> > On Mon, Dec 04, 2017 at 01:28:45PM -0800, Kees Cook wrote:
> >> On Mon, Dec 4, 2017 at 1:22 PM, Tobin C. Harding wrote:
> >> > Advice about what to use as a unique identifier i
Hi,
Recently scripts/leaking_addresses.pl was merged into the mainline with
the hope of catching leaking kernel addresses.
Would it be in scope for this script to be run by the kbuild test robot?
Excuse my very little knowledge of the kbuild test robot but would this
lead to the script being run
On Mon, 2017-12-04 at 18:23 -0200, Bruno E. O. Meneguele wrote:
> Simple but useful message log to the user in case of module appraise is
> forced and fails due to the lack of file descriptor, that might be
> caused by kmod calls to compressed modules.
[]
> diff --git a/security/integrity/ima/ima_m
On 04/12/17 05:19, Chen-Yu Tsai wrote:
> Hi,
>
> This is a small fix to get MMC performance up to proper speeds on the
Maybe a small fix for a skilled developer, but a giant leap for all
users ;-)
MMC performance goes from: (4.15-rc1)
SD: Timing buffered disk reads: 36 MB in 3.17 seconds = 1
On 04/12/17 05:19, Chen-Yu Tsai wrote:
> On the A64, the MMC module clocks are fixed in the new timing mode,
> i.e. they do not have a bit to select the mode. These clocks have
> a 2x divider somewhere between the clock and the MMC module.
>
> To be consistent with other SoCs supporting the new ti
On Mon, Dec 04, 2017 at 03:07:33PM +0100, Thomas Gleixner wrote:
> From: Thomas Gleixner
>
> Many x86 CPUs leak information to user space due to missing isolation of
> user space and kernel space page tables. There are many well documented
> ways to exploit that.
>
> The upcoming software migita
Hi Chen-Yu,
On 04/12/17 05:19, Chen-Yu Tsai wrote:
> On the A64, the MMC module clocks are fixed in the new timing mode,
> i.e. they do not have a bit to select the mode. These clocks have
> a 2x divider somewhere between the clock and the MMC module.
>
> To be consistent with other SoCs supporti
On 05.12.2017 01:59, Jeff Moyer wrote:
> Kirill Tkhai writes:
>
>> On 05.12.2017 00:52, Tejun Heo wrote:
>>> Hello, Kirill.
>>>
>>> On Tue, Dec 05, 2017 at 12:44:00AM +0300, Kirill Tkhai wrote:
> Can you please explain how this is a fundamental resource which can't
> be controlled otherwi
Signed-off-by: Scott Bauer
---
Documentation/device-mapper/dm-unstripe.txt | 82 +
1 file changed, 82 insertions(+)
create mode 100644 Documentation/device-mapper/dm-unstripe.txt
diff --git a/Documentation/device-mapper/dm-unstripe.txt
b/Documentation/device-mapper/
This device mapper module remaps and unstripes IO so it lands
solely on a single drive in a RAID 0. In a 4 drive RAID 0 the
mapper exposes 1/4th of the LBA range as a virtual drive.
Each IO to that virtual drive will land on only one of the 4
drives, selected by the user.
As an example:
Intel NVM
On Mon, Dec 04, 2017 at 02:54:46PM -0800, Andy Lutomirski wrote:
> On Mon, Dec 4, 2017 at 2:47 PM, Peter Zijlstra wrote:
> > As is __flush_tlb_single() does user and __flush_tlb_one() does
> > user+kernel.
>
> Yep. A one-liner above the function to that effect would make it
> *way* clearer what
On 05.12.2017 02:02, Tejun Heo wrote:
> Hello, Kirill.
>
> On Tue, Dec 05, 2017 at 01:49:42AM +0300, Kirill Tkhai wrote:
>>> If the only reason is kernel memory consumption protection, the only
>>> thing we need to do is making sure that memory used for aio commands
>>> are accounted against cgrou
Hello, Kirill.
On Tue, Dec 05, 2017 at 01:49:42AM +0300, Kirill Tkhai wrote:
> > If the only reason is kernel memory consumption protection, the only
> > thing we need to do is making sure that memory used for aio commands
> > are accounted against cgroup kernel memory consumption and
> > relaxing
On Mon, Dec 04, 2017 at 02:58:25PM -0800, Tejun Heo wrote:
> Hello, again.
>
> On Mon, Dec 04, 2017 at 12:22:19PM -0800, Tejun Heo wrote:
> > Hello,
> >
> > On Mon, Dec 04, 2017 at 10:44:49AM +0530, Prateek Sood wrote:
> > > Any feedback/suggestion for this patch?
> >
> > Sorry about the delay.
Hi Daniel,
Am 14.11.2017 um 00:34 schrieb Andreas Färber:
> Actions S700 has two 2Hz timers like S500, and four TIMx timers like S900.
>
> Signed-off-by: Andreas Färber
> ---
> v1 -> v2:
> * Adopted TIMER_OF_DECLARE() (Daniel)
>
> drivers/clocksource/owl-timer.c | 1 +
> 1 file changed, 1 i
Kirill Tkhai writes:
> On 05.12.2017 00:52, Tejun Heo wrote:
>> Hello, Kirill.
>>
>> On Tue, Dec 05, 2017 at 12:44:00AM +0300, Kirill Tkhai wrote:
Can you please explain how this is a fundamental resource which can't
be controlled otherwise?
>>>
>>> Currently, aio_nr and aio_max_nr are
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
drivers/net/can/flexcan.c
between commit:
29c64b17a0bc ("can: flexcan: fix VF610 state transition issue")
from Linus' tree and commit:
99b7668c04b2 ("can: flexcan: adding platform specific details for LS1021A")
fr
Hello, again.
On Mon, Dec 04, 2017 at 12:22:19PM -0800, Tejun Heo wrote:
> Hello,
>
> On Mon, Dec 04, 2017 at 10:44:49AM +0530, Prateek Sood wrote:
> > Any feedback/suggestion for this patch?
>
> Sorry about the delay. I'm a bit worried because it feels like we're
> chasing a squirrel. I'll th
On Tue, 14/11/17, Colin King wrote:
> From: Colin Ian King
> cck_poweri cannot be greated than 15 as
> is derived from the bottom 4 bits
> from riv->channels[channel -
> 1].hw_value & 0xf. Hence the check for it
> being greater than 15 is redund
On Mon, Dec 04, 2017 at 10:39:05PM +, David Howells wrote:
> Peter Zijlstra wrote:
>
> > > Good point! How about as shown in the updated patch below?
> >
> > Humm, I thought the idea was to completely remove read_barrier_depends
> > from the lkmm and memory-barriers.txt, making it an Alpha
On Mon, Dec 4, 2017 at 2:47 PM, Peter Zijlstra wrote:
> On Mon, Dec 04, 2017 at 02:22:54PM -0800, Andy Lutomirski wrote:
>
>> > +static inline void invalidate_pcid_other(void)
>> > +{
>> > + /*
>> > +* With global pages, all of the shared kenel page tables
>> > +* are set as
On Mon, Dec 04, 2017 at 02:25:43PM -0800, Andy Lutomirski wrote:
> On Mon, Dec 4, 2017 at 6:08 AM, Thomas Gleixner wrote:
> > From: Dave Hansen
> >
> > This uses INVPCID to shoot down individual lines of the user mapping
> > instead of marking the entire user map as invalid. This
> > could/might/
On 12/04/2017 01:18 PM, Thomas Gleixner wrote:
> On Mon, 4 Dec 2017, Linus Torvalds wrote:
>> On Mon, Dec 4, 2017 at 6:07 AM, Thomas Gleixner wrote:
>>> Kernel Page Table Isolation, prefix kpti_
>>>
>>>Linus, your call :)
>> I think you probably chose the right name here. The alternatives
On Mon, 4 Dec 2017, Andy Lutomirski wrote:
> On Mon, Dec 4, 2017 at 6:07 AM, Thomas Gleixner wrote:
> > From: Thomas Gleixner
> >
> > LDT is not really commonly used on 64bit so the overhead of populating the
> > fixmap entries on context switch for the rare LDT syscall users is a
> > reasonable
On Tue, 2017-12-05 at 06:45 +0800, Ming Lei wrote:
> On Mon, Dec 04, 2017 at 03:09:20PM +, Bart Van Assche wrote:
> > On Sun, 2017-12-03 at 00:31 +0800, Ming Lei wrote:
> > > Fixes: 0df21c86bdbf ("scsi: implement .get_budget and .put_budget for
> > > blk-mq")
> >
> > It might be safer to reve
Commit-ID: cdf577209aad4cdbe3455d3efa6cf631f838c55d
Gitweb: https://git.kernel.org/tip/cdf577209aad4cdbe3455d3efa6cf631f838c55d
Author: Andy Lutomirski
AuthorDate: Thu, 30 Nov 2017 07:57:57 -0800
Committer: Thomas Gleixner
CommitDate: Mon, 4 Dec 2017 23:41:42 +0100
x86/power: Fix some
On 05.12.2017 00:52, Tejun Heo wrote:
> Hello, Kirill.
>
> On Tue, Dec 05, 2017 at 12:44:00AM +0300, Kirill Tkhai wrote:
>>> Can you please explain how this is a fundamental resource which can't
>>> be controlled otherwise?
>>
>> Currently, aio_nr and aio_max_nr are global. In case of containers t
On Mon, Dec 04, 2017 at 02:22:54PM -0800, Andy Lutomirski wrote:
> > +static inline void invalidate_pcid_other(void)
> > +{
> > + /*
> > +* With global pages, all of the shared kenel page tables
> > +* are set as _PAGE_GLOBAL. We have no shared nonglobals
> > +* and
Christoph Hellwig wrote:
> [1.501264] BUG: unable to handle kernel NULL pointer dereference at
> 6714cfcb
> [1.502335] IP: rxrpc_release+0xd5/0x1c0
Is it fixed by current Linus?
In particular commit c501256406fb19c306504ee1fe41a4ea208d4245:
rxrpc: Use correct netns sou
On Mon, Dec 04, 2017 at 03:09:20PM +, Bart Van Assche wrote:
> On Sun, 2017-12-03 at 00:31 +0800, Ming Lei wrote:
> > Fixes: 0df21c86bdbf ("scsi: implement .get_budget and .put_budget for
> > blk-mq")
>
> It might be safer to revert commit 0df21c86bdbf instead of trying to fix all
> issues in
On Monday, December 4, 2017 11:38:54 PM CET Thomas Gleixner wrote:
> On Mon, 4 Dec 2017, Linus Torvalds wrote:
>
> > On Mon, Dec 4, 2017 at 2:25 PM, Rafael J. Wysocki
> > wrote:
> > >
> > > So far, resume from suspend-to-RAM (ACPI S3) is broken on all of the
> > > systems I have tested, so it is
On 12/04/2017 01:02 PM, Heiko Carstens wrote:
> On Fri, Dec 01, 2017 at 12:58:47PM -0800, Randy Dunlap wrote:
>> Hi,
>>
>> I used "maxcpus=1" on a recent x86 boot (4.15-rc1) and got 4 CPUs (all of
>> them AFAICT). When I use "nr_cpus=1", I do get a hard limit of one CPU.
>>
>>
>> A few boot log ex
On Mon, Dec 04, 2017 at 03:07:32PM +0100, Thomas Gleixner wrote:
> From: Thomas Gleixner
>
> There is currently no way to force CPU bug bits like CPU feature bits. That
> makes it impossible to set a bug bit once at boot and have it stick for all
> upcoming CPUs.
>
> Extend the force set/clear a
On Mon, Dec 04, 2017 at 02:00:16PM +0800, Yixun Lan wrote:
> From: Jian Hu
>
> Update the doc to explicitly support Meson-AXG
>
> Signed-off-by: Jian Hu
> Signed-off-by: Yixun Lan
> ---
> Documentation/devicetree/bindings/pwm/pwm-meson.txt | 2 ++
> 1 file changed, 2 insertions(+)
Reviewed-b
Peter Zijlstra wrote:
> > Good point! How about as shown in the updated patch below?
>
> Humm, I thought the idea was to completely remove read_barrier_depends
> from the lkmm and memory-barriers.txt, making it an Alpha implementation
> detail.
memory-barriers.txt explains how the barriers use
On Mon, 4 Dec 2017, Linus Torvalds wrote:
> On Mon, Dec 4, 2017 at 2:25 PM, Rafael J. Wysocki wrote:
> >
> > So far, resume from suspend-to-RAM (ACPI S3) is broken on all of the
> > systems I have tested, so it is probably safe to assume it to be
> > broken everywhere.
>
> Oh, it's definitely no
On Mon, Dec 4, 2017 at 2:34 PM, Dave Hansen wrote:
> On 12/04/2017 02:22 PM, Andy Lutomirski wrote:
>>> +
>>> + this_cpu_write(cpu_tlbstate.invalidate_other, true);
>>
>> Why do we need this extra variable instead of just looping over all
>> other ASIDs and invalidating them? It would be so
On Mon, Dec 4, 2017 at 2:25 PM, Rafael J. Wysocki wrote:
>
> So far, resume from suspend-to-RAM (ACPI S3) is broken on all of the
> systems I have tested, so it is probably safe to assume it to be
> broken everywhere.
Oh, it's definitely not broken everywhere, because I use it myself,
and was tra
On Sun, Dec 03, 2017 at 02:27:20PM +0100, Jacek Anaszewski wrote:
> Dan,
>
> On 12/01/2017 05:56 PM, Dan Murphy wrote:
> > Update the lp8860 dt binding to the LED standard where
> > the LED should have a child node and also adding a
> > LED trigger entry.
> >
> > Signed-off-by: Dan Murphy
> > --
On 12/04/2017 02:22 PM, Andy Lutomirski wrote:
>> +
>> + this_cpu_write(cpu_tlbstate.invalidate_other, true);
>
> Why do we need this extra variable instead of just looping over all
> other ASIDs and invalidating them? It would be something like:
>
> for (i = 1; i < TLB_NR_DYN_ASID
On Mon, Dec 4, 2017 at 6:08 AM, Thomas Gleixner wrote:
> From: Dave Hansen
>
> The KERNEL_PAGE_TABLE_ISOLATION code attempts to "poison" the user
> portion of the kernel page tables. It detects entries that it wants that it
> wants to poison in two ways:
>
> * Looking for addresses >= PAGE_OFFSE
201 - 300 of 1242 matches
Mail list logo
