On 08/23/2016 01:01, Bjorn Helgaas wrote:
> On Tue, Aug 16, 2016 at 08:37:15AM -0500, Bjorn Helgaas wrote:
>> On Tue, Aug 16, 2016 at 04:04:31PM +0800, Yong, Jonathan wrote:
>>> On 08/16/2016 02:59, Bjorn Helgaas wrote:
I guess I was hoping you could test these patches. Do you have any
On 6/28/16 2:06 PM, David Vrabel wrote:
> Using /proc/xen/xenbus can cause deadlocks on the atomic file position
> mutex since this file should behave like a character device and not a
> regular file. This is easiest to achive by making it a symlink to the
> existing /dev/xen/xenbus device.
>
>
2016-08-23 8:45 GMT+08:00 Paul E. McKenney :
> On Tue, Aug 23, 2016 at 06:57:20AM +0800, Wanpeng Li wrote:
>> 2016-08-22 23:30 GMT+08:00 Paul E. McKenney :
>> > Both timers and hrtimers are maintained on the outgoing CPU until
>> > CPU_DEAD
Shaun,
On 8/23/16 09:22, Shaun Tancheff wrote:
> On Mon, Aug 22, 2016 at 6:57 PM, Damien Le Moal
> wrote:
>>
>> Shaun,
>>
>> On 8/22/16 13:31, Shaun Tancheff wrote:
>> [...]
>>> -int sd_zbc_setup_discard(struct scsi_disk *sdkp, struct request *rq,
>>> -
On Mon, Aug 22, 2016 at 3:14 PM, Tom Yan wrote:
> On 23 August 2016 at 03:43, Shaun Tancheff wrote:
>>
>> Why would we enforce upper level limits on something that doesn't
>> have any?
>
> If we advertise a limit in our SATL, it makes sense that we
From: Jaeden Amero
On some devices, CD is broken so that we must force the SDHCI into test
mode and set CD, so that it always detects an SD card as present.
In order to get a device with broken CD working, we had previously
always set the SDHCI into test mode.
On Mon, Aug 22, 2016 at 6:23 PM, H. Peter Anvin wrote:
> On August 22, 2016 2:48:46 PM PDT, Andi Kleen wrote:
>>Josh Poimboeuf writes:
>>
>>> This zeroed word has no apparent purpose, so remove it.
>>>
>>> Brian Gerst says:
>>>
>>>
Since DMA addresses will effectively look like 48-bit addresses when the
memory encryption mask is set, SWIOTLB is needed if the DMA mask of the
device performing the DMA does not support 48-bits. SWIOTLB will be
initialized to create un-encrypted bounce buffers for use by these devices.
From: Xinliang Liu
Add ade and dsi DT nodes for hikey board.
Cc: Guodong Xu
Cc: Wei Xu
Cc: Rob Herring
Cc: Mark Rutland
Cc: Catalin Marinas
Cc: Will
On Tue, 23 Aug 2016 00:00:17 +0200
Pavel Machek wrote:
> On Mon 2016-08-22 22:32:23, One Thousand Gnomes wrote:
> > > why would we even have it create a /dev/ttyX for these devices in the
> > > first place. Lets just not create an uevent for it and lets not create a
> > > dev_t
> There are usb-serial devices, which could benefit from support
> btw. I would find it really useful, if the Dangerous Prototype's
> Bus Pirate would expose native /dev/i2c and /dev/spi and it's
> based on FT232.
That should just need an ldisc. I2C and SPI should at this point be sane
for
This patch adds support to be change the memory encryption attribute for
one or more memory pages.
Signed-off-by: Tom Lendacky
---
arch/x86/include/asm/cacheflush.h |3 +
arch/x86/include/asm/mem_encrypt.h | 13 ++
arch/x86/mm/mem_encrypt.c | 43
Сo6еpем для Вac пo интернет 6азy gанных noтeнциальныx клuентoв qля Bашeго
Бuзнeса! В бaзe буqym вce кoнmakmныe данныe нeo6хoquмыe gля маccовой nрoдажu
Baшuх товaрoв u уcлуr. Пo Bашeму заnpосy пришлем пpuмeр u пoqpoбную инфоpмацию.
Еcли интepecнo запроcuтe пoqрo6ноcти сeйчac МAЙЛ:
On August 22, 2016 3:47:48 PM PDT, Brian Gerst wrote:
>On Mon, Aug 22, 2016 at 6:23 PM, H. Peter Anvin wrote:
>> On August 22, 2016 2:48:46 PM PDT, Andi Kleen
>wrote:
>>>Josh Poimboeuf writes:
>>>
This zeroed
From: Mikko Rapeli
Date: Mon, 22 Aug 2016 20:32:42 +0200
> Fixes userspace compilation errors like:
>
> error: field ‘addr’ has incomplete type
> struct sockaddr_in addr; /* IP address and port to send to */
> ^
> error: field ‘addr’ has incomplete type
The struct clock_event_device has got the ->min_delta_ns, ->max_delta_ns,
->min_delta_ticks and ->max_delta_ticks members for setting the bounds
of valid deltas to be programmed.
During operation, the clockevent core uses the ->*_delta_ns versions only.
OTOH, the ->*_delta_ticks are currently
You have to post this properly to the netdev list.
If netdev is not CC:'d it doesn't get properly logged in patchwork,
and won't be applied.
From: Mikko Rapeli
Date: Mon, 22 Aug 2016 20:33:19 +0200
> Kernel uapi header are supposed to use them. Fixes userspace compile error:
>
> linux/openvswitch.h:583:2: error: unknown type name ‘uint32_t’
>
> Signed-off-by: Mikko Rapeli
Applied.
A clockevent device's rate should be configured before or at registration
and changed afterwards through clockevents_update_freq() only.
For the configuration at registration, we already have
clockevents_config_and_register().
Right now, there are no clockevents_config() users outside of the
Must be CC:'d to netdev.
From: Mikko Rapeli
Date: Mon, 22 Aug 2016 20:32:58 +0200
> Fixes userspace compile error:
>
> error: field ‘real’ has incomplete type
> struct timeval real; /* real (wall-clock) time */
>
> Signed-off-by: Mikko Rapeli
Applied.
On Mon, Aug 22, 2016 at 4:12 PM, H. Peter Anvin wrote:
>
> How about the gcc native __builtin_setjmp stuff which is supposedly better?
How new is it? The whole point was that we'd not have to worry and
wait for gcc features..
glibc doesn't use it, which worries me a bit. Has it
Hi,
On Mon, Aug 22, 2016 at 11:54:14PM +0100, One Thousand Gnomes wrote:
> On Tue, 23 Aug 2016 00:00:17 +0200
> Pavel Machek wrote:
>
> > On Mon 2016-08-22 22:32:23, One Thousand Gnomes wrote:
> > > > why would we even have it create a /dev/ttyX for these devices in the
> > > >
From: Tom Lendacky
When Secure Encrypted Virtualization is active instruction fetches are
always interpreted as being from encrypted memory so the trampoline area
must remain encrypted when SEV is active.
Signed-off-by: Tom Lendacky
---
From: Tom Lendacky
Early in the boot process, add a check to determine if the kernel is
running with Secure Encrypted Virtualization (SEV) enabled. If active,
the kernel will perform steps necessary to insure the proper kernel
initialization process is performed.
From: Tom Lendacky
Define a new KVM cpu feature for Secure Encrypted Virtualization (SEV).
The kernel will check for the presence of this feature to determine if
it is running with SEV active.
Define the SEV enable bit for the VMCB control structure. The hypervisor
will
This RFC series provides support for AMD's new Secure Encrypted
Virtualization (SEV) feature. This RFC is build upon Secure Memory
Encryption (SME) RFC.
SEV is an extension to the AMD-V architecture which supports running
multiple VMs under the control of a hypervisor. When enabled, SEV
From: SF Markus Elfring
Date: Sat, 20 Aug 2016 08:01:22 +0200
> From: Markus Elfring
> Date: Sat, 20 Aug 2016 07:50:09 +0200
>
> * Reuse existing functionality from memdup_user() instead of keeping
> duplicate source code.
>
>
The command decrypts a page of guest memory for debugging purposes.
For more information see [1], section 7.1
[1] http://support.amd.com/TechDocs/55766_SEV-KM%20API_Spec.pdf
Signed-off-by: Brijesh Singh
---
arch/x86/kvm/svm.c | 83
On Mon, Aug 22, 2016 at 10:51:27PM +0530, Sudip Mukherjee wrote:
> On Tue, Aug 23, 2016 at 12:54:17AM +0800, MingChia Chung wrote:
> > This patch fixes a minor checkpatch warnings:
> >
> > "WARNING: Block comments use a trailing */ on a separate line"
> >
> > Signed-off-by: Ming-Chia Chung
Hi,
I am using an i.MX6Q embedded board, acting as a (ethernet) gadget with
RNDIS function, connected over an USB OTG cable to a PC.
Most of the time it works fine, but in some mysterious circumstances,
a kernel panic occurs, just after attaching the OTG cable, connecting it
to the other machine:
On Mon, 2016-08-22 at 20:32 +0200, Mikko Rapeli wrote:
> Fixes userspace compilation error:
>
> error: ‘NAME_MAX’ undeclared here (not in a function)
Thanks for your effort but a patch for this, from from Tomohiro Kusumi, is
currently included in the mm tree.
>
> Signed-off-by: Mikko Rapeli
Em 19-08-2016 04:24, Aaron Lu escreveu:
On Fri, Aug 19, 2016 at 04:19:39AM -0300, Marcelo Ricardo Leitner wrote:
Hi,
Em 19-08-2016 02:29, Aaron Lu escreveu:
...
It doesn't look insane and sctp_wait_for_sndbuf may actually have
something to do with a larger sctp_chunk I suppose?
The same perf
On Monday, August 22, 2016 11:23:26 PM CEST H. Nikolaus Schaller wrote:
> I see what you mean, but kernel divides between directly connected UART and
> USB-connected UART.
>
> drivers/usb/serial/ vs. drivers/tty/serial/
That distinction purely exists for historic reasons. I'd argue that the
On Mon, Aug 22, 2016 at 3:00 PM, Sebastian Reichel wrote:
> Hi,
>
> On Mon, Aug 22, 2016 at 12:30:27PM -0500, Rob Herring wrote:
>> On Mon, Aug 22, 2016 at 12:02 PM, One Thousand Gnomes
>> wrote:
>> >> > I think there are two other valuable features
The Makefile/Kconfig currently controlling compilation of this code is:
pcieportdrv-y := portdrv_core.o portdrv_pci.o portdrv_bus.o
obj-$(CONFIG_PCIEPORTBUS) += pcieportdrv.o
drivers/pci/pcie/Kconfig:config PCIEPORTBUS
drivers/pci/pcie/Kconfig: bool "PCI Express Port Bus
The Kconfig currently controlling compilation of this code is:
drivers/pci/host/Kconfig:config PCIE_ALTERA
drivers/pci/host/Kconfig: bool "Altera PCIe controller"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially
The Kconfig currently controlling compilation of this code is:
drivers/pci/host/Kconfig:config PCI_EXYNOS
drivers/pci/host/Kconfig: bool "Samsung Exynos PCIe controller"
...meaning that it currently is not being built as a module by anyone.
Lets remove the couple traces of modular
On Mon, Aug 22, 2016 at 4:20 PM, Tom Yan wrote:
> On 22 August 2016 at 04:23, Shaun Tancheff wrote:
>> Safely overwriting the attached page to ATA format from the SCSI formatted
>> variant.
>>
>> Signed-off-by: Shaun Tancheff
The Kconfig currently controlling compilation of this code is:
drivers/pci/host/Kconfig:config PCI_HOST_COMMON
drivers/pci/host/Kconfig: bool
...meaning that it currently is not being built as a module by anyone.
Lets remove the couple trivial modular references, so that when reading
the
The Kconfig entry controlling compilation of this code is:
drivers/pci/host/Kconfig:config PCIE_DW
drivers/pci/host/Kconfig: bool
...meaning that it currently is not being built as a module by anyone.
Lets remove the couple traces of modular infrastructure use, so that
when reading the
BOOT data (such as EFI related data) is not encyrpted when the system is
booted and needs to be accessed as non-encrypted. Add support to the
early_memremap API to identify the type of data being accessed so that
the proper encryption attribute can be applied. Currently, two types
of data are
Adding general kernel support for memory encryption includes:
- Modify and create some page table macros to include the Secure Memory
Encryption (SME) memory encryption mask
- Update kernel boot support to call an SME routine that checks for and
sets the SME capability (the SME routine will
Add support to the AMD IOMMU driver to set the memory encryption mask if
memory encryption is enabled.
Signed-off-by: Tom Lendacky
---
arch/x86/include/asm/mem_encrypt.h |2 ++
arch/x86/mm/mem_encrypt.c |5 +
drivers/iommu/amd_iommu.c |
Encrypt memory areas in place when possible (e.g. zero page, etc.) so
that special handling isn't needed afterwards.
Signed-off-by: Tom Lendacky
---
arch/x86/kernel/head64.c | 93 --
arch/x86/kernel/setup.c |8
2
This patch adds the support to check if SME has been enabled and if the
mem_encrypt=on command line option is set. If both of these conditions
are true, then the encryption mask is set and the kernel is encrypted
"in place."
Signed-off-by: Tom Lendacky
---
On 2016.08.22 11:54 Srinivas Pandruvada wrote:
> I am not able to apply this patch. Can you send as a patch on top of
> Rafael's RFC 7/7. Since test takes long time, I want to apply correct
> patch.
...[cut]...
O.K. I have included a couple of changes as per the feedback from Peter
Zijlstra,
Hi Wei Yongjun,
On Sat, Aug 20, 2016 at 03:26:28PM +, Wei Yongjun wrote:
> Fixes the following sparse warning:
>
> drivers/irqchip/irq-jcore-aic.c:47:12: warning:
> symbol 'aic_irq_of_init' was not declared. Should it be static?
>
> Signed-off-by: Wei Yongjun
> ---
>
From: Mikko Rapeli
Date: Mon, 22 Aug 2016 20:32:39 +0200
> Fixes userspace compilation errors like:
>
> error: field ‘iph’ has incomplete type
> error: field ‘prefix’ has incomplete type
>
> Signed-off-by: Mikko Rapeli
Applied.
From: Mikko Rapeli
Date: Mon, 22 Aug 2016 20:32:40 +0200
> Fixes userspace compile errors like:
>
> error: field ‘mf6cc_origin’ has incomplete type
> struct sockaddr_in6 mf6cc_origin; /* Origin of mcast */
>
> Signed-off-by: Mikko Rapeli
Applied.
The ioctl will be used by qemu to issue the Secure Encrypted
Virtualization (SEV) guest commands to transition a guest into
into SEV-enabled mode.
a typical usage:
struct kvm_sev_launch_start start;
struct kvm_sev_issue_cmd data;
data.cmd = KVM_SEV_LAUNCH_START;
data.opaque =
ret = ioctl(fd,
The command initate the process to launch this guest into
SEV-enabled mode.
For more information on command structure see [1], section 6.1
[1] http://support.amd.com/TechDocs/55766_SEV-KM%20API_Spec.pdf
Signed-off-by: Brijesh Singh
---
arch/x86/kvm/svm.c | 212
This RFC series provides support for AMD's new Secure Encrypted
Virtualization (SEV) feature. This RFC is build upon Secure Memory
Encryption (SME) RFC.
SEV is an extension to the AMD-V architecture which supports running
multiple VMs under the control of a hypervisor. When enabled, SEV
On Mon, Aug 22, 2016 at 6:57 PM, Damien Le Moal wrote:
>
> Shaun,
>
> On 8/22/16 13:31, Shaun Tancheff wrote:
> [...]
>> -int sd_zbc_setup_discard(struct scsi_disk *sdkp, struct request *rq,
>> - sector_t sector, unsigned int num_sectors)
>> +int
On Mon, Aug 22, 2016 at 6:49 PM, Tom Yan wrote:
> The only 512 I can see in the old code is the one in:
>
>> - used_bytes = ALIGN(i * 8, 512);
>
> where the alignment is necessary because 'used_bytes' will be returned
> as 'size', which will be used for setting the
From: Wanpeng Li
native_smp_prepare_cpus
-> default_setup_apic_routing
-> enable_IR_x2apic
-> irq_remapping_prepare
-> intel_prepare_irq_remapping
-> intel_setup_irq_remapping
IR table is setup even if noapic boot parameter is
Hi Paul,
On Fri, Aug 19, 2016 at 06:11:19PM +0100, Paul Burton wrote:
> The MIPS GIC driver has previously iterated over bits set in a bitmap
> representing pending IRQs by calling find_first_bit, clearing that bit
> then calling find_first_bit again until all bits are clear. If multiple
>
Hi,
On Mon, Aug 22, 2016 at 05:07:06PM -0400, Marcel Holtmann wrote:
> >> Would it make sense then to define a DT binding that can cover these
> >> four cases independent of the Linux usage:
> >>
> >> a) an existing tty line discipline matched to a tty port
> >> b) a serio device using the
Hi Mikko,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.8-rc3 next-20160822]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
[Suggest to use git(>=2.9.0) format-patch --base= (or --base=auto for
convenience) to rec
On Mon 2016-08-22 22:32:23, One Thousand Gnomes wrote:
> > why would we even have it create a /dev/ttyX for these devices in the first
> > place. Lets just not create an uevent for it and lets not create a dev_t
> > for it.
>
> Because if you don't it's a regression. It's not permissible to
When System Memory Encryption (SME) is enabled, the physical address
space is reduced. Adjust the x86_phys_bits value to reflect this
reduction.
Signed-off-by: Tom Lendacky
---
arch/x86/kernel/cpu/common.c |2 ++
1 file changed, 2 insertions(+)
diff --git
This patch adds a Documenation entry to decribe the AMD Secure Memory
Encryption (SME) feature.
Signed-off-by: Tom Lendacky
---
Documentation/x86/amd-memory-encryption.txt | 35 +++
1 file changed, 35 insertions(+)
create mode 100644
On August 22, 2016 3:23:06 PM PDT, Linus Torvalds
wrote:
>On Sun, Aug 21, 2016 at 10:52 AM, Linus Torvalds
> wrote:
>> On Sat, Aug 20, 2016 at 11:42 PM, Al Viro
>wrote:
>>>
>>> It's not exactly
With the yet to come introduction of NTP correction awareness to the
clockevent core, drivers should report their valid ranges in units of
cycles to the latter.
Currently, the x86's uv rtc clockevent device is initialized as follows:
clock_event_device_uv.min_delta_ns = NSEC_PER_SEC /
Currently, the em_sti driver prepares and enables the needed clock in
em_sti_enable(), potentially called through its clockevent device's
->set_state_oneshot().
However, the clk_prepare() step may sleep whereas tick_program_event() and
thus, ->set_state_oneshot(), can be called in atomic context.
amically
[19/22] clockevents: purge ->min_delta_ns and ->max_delta_ns
gets rid of the ->*_delta_ns alltogether.
The remaining patches, i.e. [20-22/22], correspond to the former
[1-3/3] from v3.
Tested on next-20160816. Applies to next-20160822.
In case that you want me to proceed
With the upcoming NTP correction related rate adjustments to be implemented
in the clockevents core, the latter needs to get informed about every rate
change of a clockevent device made after its registration.
Currently, em_sti violates this requirement in that it registers its
clockevent device
With the upcoming NTP correction related rate adjustments to be implemented
in the clockevents core, the latter needs to get informed about every rate
change of a clockevent device made after its registration.
Currently, sh_cmt violates this requirement in that it registers its
clockevent device
With the yet to come introduction of NTP correction awareness to the
clockevent core, drivers should report their valid ranges in units of
cycles to the latter.
Currently, the tile's timer clockevent device is initialized as follows:
evt->max_delta_ns = clockevent_delta2ns(MAX_TICK, evt);
and
With the upcoming NTP correction related rate adjustments to be implemented
in the clockevents core, the latter needs to get informed about every rate
change of a clockevent device made after its registration.
Currently, sh_tmu violates this requirement in that it registers its
clockevent device
From: Tom Lendacky
When a guest causes a NPF which requires emulation, KVM sometimes walks
the guest page tables to translate the GVA to a GPA. This is unnecessary
most of the time on AMD hardware since the hardware provides the GPA in
EXITINFO2.
The only exception
From: Tom Lendacky
AMD hardware adds two additional bits to aid in nested page fault handling.
Bit 32 - NPF occurred while translating the guest's final physical address
Bit 33 - NPF occurred while translating the guest page tables
The guest page tables fault indicator
With the yet to come introduction of NTP correction awareness to the
clockevent core, drivers should report their valid ranges in units of
cycles to the latter.
Currently, the s390's CPU timer clockevent device is initialized as
follows:
cd->min_delta_ns= 1;
cd->max_delta_ns=
Shaun,
On 8/22/16 13:31, Shaun Tancheff wrote:
[...]
> -int sd_zbc_setup_discard(struct scsi_disk *sdkp, struct request *rq,
> - sector_t sector, unsigned int num_sectors)
> +int sd_zbc_setup_discard(struct scsi_cmnd *cmd)
> {
> - struct blk_zone *zone;
> + struct
From: Tom Lendacky
DMA must be performed to memory that is not mapped encrypted when running
with SEV active. So if SEV is active, do not return the encryption mask
to the IOMMU.
Signed-off-by: Tom Lendacky
---
arch/x86/mm/mem_encrypt.c |2
From: Tom Lendacky
When Secure Encrypted Virtualization (SEV) is active, BOOT data (such as
EFI related data) is encrypted and needs to be access as such. Update the
architecture override in early_memremap to keep the encryption attribute
when mapping this data.
From: Tom Lendacky
Update the I/O interception support to add the kvm_fast_pio_in function
to speed up the in instruction similar to the out instruction.
Signed-off-by: Tom Lendacky
---
arch/x86/include/asm/kvm_host.h |1 +
From: Linus Torvalds
Date: Mon, 22 Aug 2016 16:48:00 -0700
> How new is it? The whole point was that we'd not have to worry and
> wait for gcc features..
It's been around for a long time.
I'd say at least gcc-3.0 and later support it.
On Tue, Aug 23, 2016 at 06:57:20AM +0800, Wanpeng Li wrote:
> 2016-08-22 23:30 GMT+08:00 Paul E. McKenney :
> > Both timers and hrtimers are maintained on the outgoing CPU until
> > CPU_DEAD time, at which point they are migrated to a surviving CPU. If a
> >
Hi Zhiyong,
[auto build test ERROR on robh/for-next]
[also build test ERROR on v4.8-rc3 next-20160822]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
[Suggest to use git(>=2.9.0) format-patch --base= (or --base=auto for
convenience) to rec
Hi,
On Tue, Aug 23, 2016 at 01:15:21AM +0100, One Thousand Gnomes wrote:
> > > That would still be a regression. Not everyone even uses the kernel
> > > bluetooth stack. It would only return EBUSY if you had done an "up"
> > > on it via the direct bluetooth stack.
> >
> > So it returns EBUSY
On Mon, Aug 22, 2016 at 4:33 PM, Josh Poimboeuf wrote:
> On Mon, Aug 22, 2016 at 03:27:19PM -0500, Josh Poimboeuf wrote:
>> On Fri, Aug 19, 2016 at 04:55:22PM -0500, Josh Poimboeuf wrote:
>> > On Fri, Aug 19, 2016 at 11:27:18AM -0700, Kees Cook wrote:
>> > > On Thu, Aug 18,
On Mon, 22 Aug 2016, Huang Rui wrote:
> Hi Peter, Vince
>
> On Fri, Aug 19, 2016 at 12:01:30PM +0200, Peter Zijlstra wrote:
> > On Thu, Aug 18, 2016 at 10:46:31AM -0400, Vince Weaver wrote:
> > > On Thu, 18 Aug 2016, Vince Weaver wrote:
> > >
> > > > Tried the perf_fuzzer on my A10
On (08/22/16 09:10), Joe Perches wrote:
>
> (adding Kay Sievers who wrote most of this)
ok, thanks. then I'll add http://marc.info/?l=linux-kernel=146717692431893
for more information.
-ss
The Kconfig currently controlling compilation of this code is:
drivers/pci/host/Kconfig:config PCIE_ALTERA_MSI
drivers/pci/host/Kconfig: bool "Altera PCIe MSI feature"
...meaning that it currently is not being built as a module by anyone.
Lets remove the couple traces of modular
Am Montag, 22 August 2016, 11:36:43 schrieb Dave Young:
> On 08/22/16 at 12:25am, Thiago Jung Bauermann wrote:
> > Am Montag, 22 August 2016, 11:17:45 schrieb Dave Young:
> > > On 08/18/16 at 06:09pm, Thiago Jung Bauermann wrote:
> > > > Am Donnerstag, 18 August 2016, 17:03:30 schrieb Dave Young:
[Re: [PATCH -next] PCI/PCIe: make DPC explicitly non-modular] On 22/08/2016
(Mon 14:44) Bjorn Helgaas wrote:
> Hi Paul,
>
> On Thu, Jul 28, 2016 at 05:28:02PM -0400, Paul Gortmaker wrote:
[...]
> >
> > Yep, not to worry, I've still got the following patches pending for-4.9:
> >
> > $ grep
Am Montag, 22 August 2016, 15:22:00 schrieb Dave Young:
> On 08/22/16 at 12:38am, Thiago Jung Bauermann wrote:
> > Am Montag, 22 August 2016, 11:21:35 schrieb Dave Young:
> > > On 08/13/16 at 12:18am, Thiago Jung Bauermann wrote:
> > > > diff --git a/arch/powerpc/kernel/machine_kexec_64.c
> > > >
On Mon, Aug 22, 2016 at 10:53 AM, Paul E. McKenney
wrote:
> On Mon, Aug 22, 2016 at 03:15:35PM +0200, Arnd Bergmann wrote:
>> On Wednesday, August 17, 2016 2:42:11 PM CEST Kees Cook wrote:
>> > +
>> > +/*
>> > + * Since detected data corruption should stop operation on
tty_port_close handles much of the common parts of tty close. Convert
uart_close to use it and move the serial_core specific parts into
tty_port.shutdown function. This will be needed to use tty_port functions
directly from in kernel clients.
This change causes ops->stop_rx() to be called after
Add support to check if memory encryption is active in the kernel and that
it has been enabled on the AP. If memory encryption is active in the kernel
but has not been enabled on the AP then do not allow the AP to continue
start up.
Signed-off-by: Tom Lendacky
---
tty_port_open handles much of the common parts of tty opening. Convert
uart_open to use it and move the serial_core specific parts into
tty_port.activate function. This will be needed to use tty_port functions
directly from in kernel clients.
The tricky part is uart_port_startup can return
Update the cpu features to include identifying and reporting on the
Secure Memory Encryption feature.
Signed-off-by: Tom Lendacky
---
arch/x86/include/asm/cpufeature.h|7 +--
arch/x86/include/asm/cpufeatures.h |5 -
This adds support to be able to either encrypt or decrypt data during
the early stages of booting the kernel. This does not change the memory
encryption attribute - it is used for ensuring that data present in
either an encrypted or un-encrypted memory area is in the proper state
(for example the
From: Mikko Rapeli
Date: Mon, 22 Aug 2016 20:32:44 +0200
> Fixes userspace compiler error:
>
> error: ‘IFNAMSIZ’ undeclared here (not in a function)
>
> Suggested by Frans Klaver on lkml message
> <20150530195223.ga15...@bugger.home>.
>
>
The command encrypts a region of guest memory for debugging purposes.
For more information see [1], section 7.2
[1] http://support.amd.com/TechDocs/55766_SEV-KM%20API_Spec.pdf
Signed-off-by: Brijesh Singh
---
arch/x86/kvm/svm.c | 100
Signed-off-by: Brijesh Singh
---
arch/x86/kvm/svm.c | 23 +++
1 file changed, 23 insertions(+)
diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
index 4af195d..88b8f89 100644
--- a/arch/x86/kvm/svm.c
+++ b/arch/x86/kvm/svm.c
@@ -5779,6 +5779,25 @@
The command is used for encrypting guest memory region.
For more information see [1], section 6.2
[1] http://support.amd.com/TechDocs/55766_SEV-KM%20API_Spec.pdf
Signed-off-by: Brijesh Singh
---
arch/x86/kvm/svm.c | 126
From: Mikko Rapeli
Date: Mon, 22 Aug 2016 20:32:48 +0200
> Fixes userspace compile errors like:
>
> error: field ‘vifc_lcl_addr’ has incomplete type
> struct in_addr vifc_lcl_addr; /* Local interface address */
>
> Signed-off-by: Mikko Rapeli
The command is used to query the SEV guest status.
For more information see [1], section 6.10
[1] http://support.amd.com/TechDocs/55766_SEV-KM%20API_Spec.pdf
Signed-off-by: Brijesh Singh
---
arch/x86/kvm/svm.c | 41 +
1 file
601 - 700 of 2074 matches
Mail list logo