Boot data (such as EFI related data) is not encrypted when the system is
booted and needs to be mapped decrypted. Add support to apply the proper
attributes to the EFI page tables and to the early_memremap and memremap
APIs to identify the type of data being accessed so that the proper
encryption
Update the efi_mem_type() to return EFI_RESERVED_TYPE instead of a
hardcoded 0.
Signed-off-by: Tom Lendacky
---
arch/x86/platform/efi/efi.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/platform/efi/efi.c b/arch/x86/platform/efi/efi.c
index a15cf81..6407103
When Secure Memory Encryption is enabled, the trampoline area must not
be encrypted. A CPU running in real mode will not be able to decrypt
memory that has been encrypted because it will not be able to use addresses
with the memory encryption mask.
Signed-off-by: Tom Lendacky
---
arch/x86/realmo
Add support for changing the memory encryption attribute for one or more
memory pages.
Signed-off-by: Tom Lendacky
---
arch/x86/include/asm/cacheflush.h |3 ++
arch/x86/mm/pageattr.c| 66 +
2 files changed, 69 insertions(+)
diff --git a/arch
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 decrypted bounce buffers for use by these devices.
Signed-off-b
Persistent memory is expected to persist across reboots. The encryption
key used by SME will change across reboots which will result in corrupted
persistent memory. Persistent memory is handed out by block devices
through memory remapping functions, so be sure not to map this memory as
encrypted.
Add warnings to let the user know when bounce buffers are being used for
DMA when SME is active. Since the bounce buffers are not in encrypted
memory, these notifications are to allow the user to determine some
appropriate action - if necessary.
Signed-off-by: Tom Lendacky
---
arch/x86/include/
For now, disable the AMD IOMMU if memory encryption is active. A future
patch will re-enable the function with full memory encryption support.
Signed-off-by: Tom Lendacky
---
drivers/iommu/amd_iommu_init.c |7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/iommu/amd_iommu_init
Use memremap() to map the setup data. This simplifies the code and will
make the appropriate decision as to whether a RAM remapping can be done
or if a fallback to ioremap_cache() is needed (which includes checking
PageHighMem).
Signed-off-by: Tom Lendacky
---
arch/x86/kernel/kdebugfs.c | 30
Update the KVM support to include the memory encryption mask when creating
and using nested page tables.
Signed-off-by: Tom Lendacky
---
arch/x86/include/asm/kvm_host.h |3 ++-
arch/x86/kvm/mmu.c |8 ++--
arch/x86/kvm/vmx.c |3 ++-
arch/x86/kvm/x86.c
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 set the SYS_CFG MSR bit to enable
memory encryption on that AP and allow the AP to continue start up.
Sign
Use memremap() to map the setup data. This will make the appropriate
decision as to whether a RAM remapping can be done or if a fallback to
ioremap_cache() is needed (similar to the setup data debugfs support).
Signed-off-by: Tom Lendacky
---
arch/x86/kernel/ksysfs.c | 27 ++--
Since video memory needs to be accessed decrypted, be sure that the
memory encryption mask is not set for the video ranges.
Signed-off-by: Tom Lendacky
---
arch/x86/include/asm/vga.h | 13 +
drivers/gpu/drm/drm_gem.c|2 ++
drivers/gpu/drm/drm_vm.c |4 +
This patch adds the support to encrypt the kernel in-place. This is
done by creating new page mappings for the kernel - a decrypted
write-protected mapping and an encrypted mapping. The kernel is encyrpted
by copying the kernel through a temporary buffer.
Signed-off-by: Tom Lendacky
---
arch/x86
Provide support so that kexec can be used to boot a kernel when SME is
enabled.
Support is needed to allocate pages for kexec without encryption. This
is needed in order to be able to reboot in the kernel in the same manner
as originally booted.
Additionally, when shutting down all of the CPUs w
This patch adds the support to check if SME has been enabled and if
memory encryption should be activated (checking of command line option
based on the configuration of the default state). If memory encryption
is to be activated, then the encryption mask is set and the kernel is
encrypted "in plac
Thank you Vito for the report.
The patch you cited actually resolves a similar backward compatibility
problem for traceroute.
I suspect the problem here is that there's a local error queued on the
error queue after an ICMP message. ping apparently expect the
sk->sk_err to be set for the local err
Add to the early_memremap support to be able to specify encrypted and
decrypted mappings with and without write-protection. The use of
write-protection is necessary when encrypting data "in place". The
write-protect attribute is considered cacheable for loads, but not
stores. This implies that the
On Wed, 2017-02-15 at 09:17 -0500, Vivek Goyal wrote:
> On Tue, Feb 14, 2017 at 03:45:55PM -0800, James Bottomley wrote:
> > On Tue, 2017-02-14 at 18:03 -0500, Vivek Goyal wrote:
[...]
> > > Given we have already shifted the uid/gid for shiftfs inode, I am
> > > wondering that why can't we simply
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 | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/arch/x86/
On Thu, Feb 16, 2017 at 10:50 AM, Soheil Hassas Yeganeh
wrote:
> Thank you Vito for the report.
>
> The patch you cited actually resolves a similar backward compatibility
> problem for traceroute.
>
> I suspect the problem here is that there's a local error queued on the
> error queue after an ICM
On Wed, 2017-02-15 at 21:59 -0800, Guenter Roeck wrote:
> On 02/15/2017 02:41 PM, Ben Hutchings wrote:
> > This is the start of the stable review cycle for the 3.2.85 release.
> > There are 126 patches in this series, which will be posted as responses
> > to this one. If anyone has any issues with
On Wed, 2017-02-15 at 15:34 -0500, Vivek Goyal wrote:
> On Sat, Feb 04, 2017 at 11:19:32AM -0800, James Bottomley wrote:
>
> [..]
> > +static struct dentry *shiftfs_lookup(struct inode *dir, struct
> > dentry *dentry,
> > +unsigned int flags)
> > +{
> > + struct d
來信已收到，
早安~
採購人員你好：
我司專門生產交換式電源供應器、USB充電器、POE供電，
全球眾多知名公司都是我們長期合作的客戶，
例如PHILIPS、HP、TOSHIBA、LITEON…等，
我們擁有各國眾多安規認證，
還有提供專業 ODM、OEM 服務
我們公司位於台中，歡迎來坐坐，
誠摯的希望與您合作。
期待你的回覆，將不勝感激。
吉密科技
林榮宗
0422587996
gme.po...@msa.hinet.net
如寄錯請轉交，謝謝
On Thu, 2017-02-16 at 09:25 +0800, Wei Fang wrote:
> Hi, Ben,
>
> Commit d05c5f7ba164 "vfs,mm: fix return value of read() at s_maxbytes"
> need be backported with this patch, otherwise we'll get an error when
> reading at the end of the file.
[...]
Sorry, I should have seen the notes for this com
On Thu, 2017-02-16 at 09:42 +0800, Hangbin Liu wrote:
> > 2017-02-16 6:41 GMT+08:00 Ben Hutchings :
> > 3.2.85-rc1 review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Hangbin Liu
> >
> > commit 24803f38a5c0b6c57ed800b47e695f9ce474bc3a upstre
KVM requests are not used with one API, but are a mix of open-coded
setting and kicking, which is what this series aims to normalize.
The main problem is described in comment of patch 1:
There are three main kinds of requests
1) requests from a VCPU to itself,
2) requests for a remote VCPU,
3)
Just to complete the encapsulation.
Signed-off-by: Radim Krčmář
---
arch/mips/kvm/trap_emul.c | 2 +-
arch/powerpc/kvm/booke.c | 2 +-
arch/powerpc/kvm/powerpc.c | 4 ++--
arch/s390/kvm/kvm-s390.c | 2 +-
arch/x86/kvm/x86.c | 4 ++--
include/linux/kvm_host.h | 5 +
6 files cha
kvm_make_request was a wrapper that added barriers to bit_set and
kvm_check_request did the same for bit_test and bit_check, but the name
was not very obvious and we were also lacking operations that cover
bit_test and bit_clear, which resulted in an inconsistent use.
The renaming:
kvm_request_s
A macro to optimize requests that do not need a memory barrier because
they have no dependencies. An architecture can implement a function
that says which requests do not need memory barriers when handling them.
Signed-off-by: Radim Krčmář
---
include/linux/kvm_host.h | 41 +
The leading underscores mean that the call is just a bitop wrapper.
Switch all users of open-coded set/check/test to kvm_request ones.
Automated by coccinelle script:
@@
expression VCPU, REQ;
@@
-set_bit(REQ, &VCPU->requests)
+__kvm_request_set(REQ, VCPU)
@@
expression VCPU, REQ;
Use __kvm_request_set to avoid repeated use of wmb().
kvm_make_all_cpus_request is also a candidate for renaming.
Signed-off-by: Radim Krčmář
---
virt/kvm/kvm_main.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
index 934f135c0
On Thu, 2017-02-16 at 07:56 +0100, Linus Lüssing wrote:
> On Wed, Feb 15, 2017 at 10:41:34PM +, Ben Hutchings wrote:
> > 3.2.85-rc1 review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Linus Lüssing
> >
> > commit 9799c50372b23ed774791bdb
2017-02-15 23:08 GMT+01:00 Rob Herring :
> On Tue, Feb 07, 2017 at 05:41:16PM +0100, Bartosz Golaszewski wrote:
>> This makes the example more or less correspond with the da850-evm
>> hardware setup.
>>
>> Signed-off-by: Bartosz Golaszewski
>> ---
>> .../devicetree/bindings/media/ti,da850-vpif.tx
On Thu, 2017-02-16 at 09:31 +0100, Arnd Bergmann wrote:
> > On Wed, Feb 15, 2017 at 11:41 PM, Ben Hutchings
> > wrote:
> > 3.16.40-rc1 review patch. If anyone has any objections, please let me know.
> >
> > From: Arnd Bergmann
> >
> > commit d0fe85e95f56a01a49e4893aa26263e8aee67eef upstream.
On Thu, Feb 16, 2017 at 10:52:19AM -0500, Soheil Hassas Yeganeh wrote:
> On Thu, Feb 16, 2017 at 10:50 AM, Soheil Hassas Yeganeh
> wrote:
> > Thank you Vito for the report.
> >
> > The patch you cited actually resolves a similar backward compatibility
> > problem for traceroute.
> >
> > I suspect
Limiting transfers to MAX_SPI_FRAMESIZE was not expected by the upper
layers, as tpm_tis has no such limitation. Add a loop to hide that
limitation.
Cc:
Fixes: 0edbfea537d1 ("tpm/tpm_tis_spi: Add support for spi phy")
Signed-off-by: Alexander Steffen
Signed-off-by: Peter Huewe
---
drivers/char
Abort the transfer with ETIMEDOUT when the TPM signals more than
TPM_RETRY wait states. Continuing with the transfer in this state
will only lead to arbitrary failures in other parts of the code.
Cc:
Fixes: 0edbfea537d1 ("tpm/tpm_tis_spi: Add support for spi phy")
Signed-off-by: Alexander Steffen
During our testing it showed that unfortunately the whole native spi tpm driver
was more or less non-functional since it was merged, e.g. the wrong byte for
waitstate handling was used and transfers larger than 64 bytes did not work at
all.
This was probably caused by the merging of the different
Wait states are signaled in the last byte received from the TPM in
response to the header, not the first byte. Check rx_buf[3] instead of
rx_buf[0].
Cc:
Fixes: 0edbfea537d1 ("tpm/tpm_tis_spi: Add support for spi phy")
Signed-off-by: Alexander Steffen
Signed-off-by: Peter Huewe
---
drivers/char
The algorithm for sending data to the TPM is mostly identical to the
algorithm for receiving data from the TPM, so a single function is
sufficient to handle both cases.
This is a prequisite for all the other fixes, so we don't have to fix
everything twice (send/receive)
Cc:
[prerequisite for oth
Testing the implementation with a Raspberry Pi 2 showed that under some
circumstances its SPI master erroneously releases the CS line before the
transfer is complete, i.e. before the end of the last clock. In this case
the TPM ignores the transfer and misses for example the GO command. The
driver i
On Wed, Feb 15, 2017 at 04:37:49PM -0500, Waiman Long wrote:
> The cpu argument in the function prototype of vcpu_is_preempted()
> is changed from int to long. That makes it easier to provide a better
> optimized assembly version of that function.
>
> For Xen, vcpu_is_preempted(long) calls xen_vcp
On 02/15/2017 03:50 PM, thor.tha...@linux.intel.com wrote:
> From: Thor Thayer
>
> Add the Altera Arria10 System Resource Reset Controller to the MFD
>
> Signed-off-by: Thor Thayer
Nit:
Please have the commit header as "ARM: dts: socfpga:"
Otherwise,
Acked-by: Dinh Nguyen
Dinh
On Thursday, December 29, 2016 11:45:03 PM CET Nikita Yushchenko wrote:
>
> static int __swiotlb_dma_supported(struct device *hwdev, u64 mask)
> {
> +#ifdef CONFIG_PCI
> + if (dev_is_pci(hwdev)) {
> + struct pci_dev *pdev = to_pci_dev(hwdev);
> + struct pci_host
T: Bus=01 Lev=02 Prnt=02 Port=02 Cnt=01 Dev#= 7 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1
P: Vendor=1eda ProdID=2315 Rev=01.08
S: Manufacturer=ATHEROS
S: Product=USB2.0 WLAN
S: SerialNumber=12345
C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs=
Thanks everyone. Sorry about the mess :)
On 02/15/2017 10:23 PM, Michael Ellerman wrote:
> Jon Derrick writes:
>
>> PPC's 'opal' match pattern also matches block/sed-opal.c, where it looks
>> like the 'arch/powerpc' file pattern should be enough to match powerpc
>> opal code by itself. Remove th
Spaces should be added around operators to improve readability
and are required in some cases.
Signed-off-by: Shiva Kerdel
---
drivers/staging/ks7010/ks_hostif.c | 2 +-
drivers/staging/ks7010/ks_hostif.h | 64 +-
drivers/staging/ks7010/ks_wlan.h |
Hi Javier,
> If the driver is built as a module, autoload won't work because the module
> alias information is not filled. So user-space can't match the registered
> device with the corresponding module.
>
> Export the module alias information using the MODULE_DEVICE_TABLE() macro.
>
> Before th
2017-02-15 15:43+0100, Paolo Bonzini:
> The purpose of the KVM_SET_SIGNAL_MASK API is to let userspace "kick"
> a VCPU out of KVM_RUN through a POSIX signal. A signal is attached
> to a dummy signal handler; by blocking the signal outside KVM_RUN and
> unblocking it inside, this possible race is c
Hi,
> The Marvell devices may have many gpio pins, and hence for wakeup
> on these out-of-band pins, the chip needs to be told which pin is
> to be used for wakeup, using an hci command.
>
> Thus, we read the pin number etc from the device tree node and send
> a command to the chip.
>
> Signed-o
On Thursday, February 9, 2017 12:52:50 PM CET Brian Norris wrote:
> It's useful to get testing on these features on various boards (e.g., on
> KernelCI), and (when they're working) the ramoops feature is extremely
> helpful for debugging live systems.
>
> Signed-off-by: Brian Norris
> ---
> + ARM
2017-02-15 15:44+0100, Paolo Bonzini:
> Signed-off-by: Paolo Bonzini
Reviewed-by: Radim Krčmář
> ---
> arch/x86/kvm/vmx.c | 30 --
> 1 file changed, 8 insertions(+), 22 deletions(-)
>
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> index bca60665d55d..0e0b
Hi Jeffy,
> Use irqflags parsed from dt.
>
> Signed-off-by: Jeffy Chen
> Reviewed-by: Brian Norris
> ---
>
> Changes in v2: None
>
> drivers/bluetooth/btmrvl_sdio.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
all 3 patches have been applied to bluetooth-next tree.
Regards
Marc
2017-02-15 23:00+0100, Paolo Bonzini:
> This will make it a bit simpler to handle multiple address spaces
> in gfn_to_hva_cache.
>
> Signed-off-by: Paolo Bonzini
> ---
Reviewed-by: Radim Krčmář
> virt/kvm/kvm_main.c | 21 ++---
> 1 file changed, 14 insertions(+), 7 deletions(-
On (02/16/17 07:10), Tony Lindgren wrote:
[..]
> > > > [..]
> > > > > Below is another issue I noticed caused by commit f975237b7682 that
> > > > > I noticed during booting.
> > > >
> > > > do you mean that with f975237b7682 you _always_ see that illegal RCU
> > > > usage warning?
> > >
> > > Yea
On 15/02/2017 14:33, Daniel Bristot de Oliveira wrote:
[1] For the sake of completeness:
- dl_se->deadline = Absolute deadline
- dl_se->dl_deadline = Relative deadline
Daniel's note [1] reminds me that, would it be worth a rename of these, for the
sake of clarity, e.g.:
-) abs_deadline vs rel_d
Hi Dmitry,
> T: Bus=01 Lev=01 Prnt=01 Port=07 Cnt=04 Dev#= 5 Spd=12 MxCh= 0
> D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
> P: Vendor=04ca ProdID=3018 Rev=00.01
> C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
> I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> I:
Hi Javier,
> The driver only has runtime but no build time dependency with QCOM_SMD &&
> QCOM_WCNSS_CTRL. So it can be built for testing purposes if COMPILE_TEST
> option is enabled.
>
> This is useful to have more build coverage and make sure that the driver
> is not affected by changes that cou
Hi Colin,
> trivial fix to spelling mistake in BT_ERR error message
>
> Signed-off-by: Colin Ian King
> ---
> drivers/bluetooth/btmrvl_main.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
patch has been applied to bluetooth-next tree.
Regards
Marcel
On Thu, Feb 16, 2017 at 11:28:49AM +0100, Oliver Neukum wrote:
> Am Dienstag, den 07.02.2017, 22:01 -0600 schrieb Gustavo A. R. Silva:
> > The condition modex % 16 cannot be true when modex value is equal to
> > 640
> > The condition du & 0xff cannot be true when du value is equal to
> > 0x1400
> >
Hi Colin,
> trivial fix to spelling mistake in BT_ERR_RATELIMITED error message
>
> Signed-off-by: Colin Ian King
> ---
> net/bluetooth/hci_event.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
patch has been applied to bluetooth-next tree.
Regards
Marcel
On 02/15/2017 05:19 PM, Maxime Ripard wrote:
> Hi,
>
> This is a respin of the previous serie called "Support fast framebuffer
> panning for i.MX6" made by Stefan 6 monthes ago. The imx6 bits have been
> removed, and the comments that were made at that time fixed (hopefully).
>
> Let me know what
Hi,
On Thu, Feb 16, 2017 at 10:03:05AM -0500, Agustin Vega-Frias wrote:
> This adds a new dynamic PMU to the Perf Events framework to program
> and control the L3 cache PMUs in some Qualcomm Technologies SOCs.
>
> The driver supports a distributed cache architecture where the overall
> cache is c
On Thu, Feb 16, 2017 at 07:51:58AM -0800, James Bottomley wrote:
[..]
> > Two levels of checks will simplify this a bit. Top level inode will
> > belong to the user namespace of caller and checks should pass. And
> > mounter's creds will have ownership over the real inode so no
> > additional n
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-linus
Fix a use after free bug introduced in 4.2 and using an uninitialized value
introduced in 4.9.
Thanks,
Miklos
---
Miklos Szeredi (1):
fuse: fix uninitialized flags in pipe_buffer
Sahi
On Thu, 16 Feb 2017 17:36:07 +0100
Tommaso Cucinotta wrote:
> On 15/02/2017 14:33, Daniel Bristot de Oliveira wrote:
> > [1] For the sake of completeness:
> > - dl_se->deadline = Absolute deadline
> > - dl_se->dl_deadline = Relative deadline
> Daniel's note [1] reminds me that, would it be wort
From: Miklos Szeredi
Flags (PIPE_BUF_FLAG_PACKET, PIPE_BUF_FLAG_GIFT) could remain on the unused
part of the pipe ring buffer. Previously splice_to_pipe() left the flags
value alone, which could result in incorrect behavior.
Uninitialized flags appears to have been there from the introduction o
On Tue, Feb 14, 2017 at 5:52 PM, Krzysztof Kozlowski wrote:
> On Fri, Feb 10, 2017 at 12:30:48PM +0100, Sylwester Nawrocki wrote:
>> On 02/09/2017 07:56 PM, Krzysztof Kozlowski wrote:
>> > On Thu, Feb 09, 2017 at 04:19:57PM +0100, Arnd Bergmann wrote:
>>
>> > 2. Update of frequency (used in DTS as
On Wed, Feb 15, 2017 at 04:37:50PM -0500, Waiman Long wrote:
> +/*
> + * Hand-optimize version for x86-64 to avoid 8 64-bit register saving and
> + * restoring to/from the stack. It is assumed that the preempted value
> + * is at an offset of 16 from the beginning of the kvm_steal_time structure
>
Hi Philipp,
On 02/16/2017 04:30 AM, Philipp Zabel wrote:
Hi Thor,
thank you for the patch. A few comments below:
On Wed, 2017-02-15 at 15:50 -0600, thor.tha...@linux.intel.com wrote:
From: Thor Thayer
This patch adds the reset controller functionality to the Arria10
System Resource Manager.
Hi Alan,
On Wed, 15 Feb 2017, Alan Tull wrote:
Currently if a user applies > 1 overlays to a region
and removes them, we get a slow warning from devm_kfree.
because the pointer to the FPGA image info was overwritten.
This commit adds a list to keep track of overlays applied
to each FPGA regi
On 02/16/2017 10:12 AM, Dinh Nguyen wrote:
On 02/15/2017 03:50 PM, thor.tha...@linux.intel.com wrote:
From: Thor Thayer
Add the Altera Arria10 System Resource Reset Controller to the MFD
Signed-off-by: Thor Thayer
Nit:
Please have the commit header as "ARM: dts: socfpga:"
Otherwise,
A
On 16 February 2017 at 12:43, Tobias Jakobi
wrote:
> Hello,
>
> I was wondering about the following. Wasn't there some strict
> requirement about code going upstream, which also included that there
> was a full open-source driver stack for it?
>
> I don't see how this is the case for Mali, neither
On Thu, 2017-02-16 at 11:42 -0500, Vivek Goyal wrote:
> On Thu, Feb 16, 2017 at 07:51:58AM -0800, James Bottomley wrote:
>
> [..]
> > > Two levels of checks will simplify this a bit. Top level inode
> > > will belong to the user namespace of caller and checks should
> > > pass. And mounter's cre
On 06/02/2017 at 15:35:55 +0100, Ludovic Desroches wrote:
> On Mon, Jan 30, 2017 at 06:25:33PM +0100, Alexandre Belloni wrote:
> > When going to suspend, the I2C registers may be lost because the power to
> > VDDcore is cut. Save them and restore them when resuming.
> >
> > Signed-off-by: Alexandr
2017-02-15 23:00+0100, Paolo Bonzini:
> This will make it easier to support multiple address spaces in
> kvm_gfn_to_hva_cache_init. Instead of having to check the address
> space id, we can keep on checking just the generation number.
>
> Signed-off-by: Paolo Bonzini
> ---
Reviewed-by: Radim Kr
After commit 66d228a2bf03 ("regulator: core: Don't use regulators as
supplies until the parent is bound"), input supplies aren't resolved
if the input supplies parent device has not been bound. This prevent
regulators to hold an invalid reference if its supply parent device
driver probe is deferred
2017-02-15 23:00+0100, Paolo Bonzini:
> From: "Cao, Lei"
>
> Provide versions of struct gfn_to_hva_cache functions that
> take vcpu as a parameter instead of struct kvm. The existing functions
> are not needed anymore, so delete them. This allows dirty pages to
> be logged in the vcpu dirty rin
From: Cristian Birsan
The A13 hardware line is shared by SPI and MCI1 controller.This patch
disables the SPI controller so that the MCI1 (the big MMC card slot) can
be used.
Signed-off-by: Cristian Birsan
---
arch/arm/boot/dts/at91sam9x5ek.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletio
On Wed, Feb 15, 2017 at 05:08:09PM +0800, Jason Wang wrote:
> We set queues before reset which will cause a crash[1]. This is
> because is_xdp_raw_buffer_queue() depends on the old xdp queue pairs
> number to do the correct detection. So fix this by:
>
> - set queues after reset, to keep the old v
On Fri, Feb 3, 2017 at 11:47 AM, Arnd Bergmann wrote:
> gcc-4.8 warns about '{0}' being used an an initializer for nested structures:
>
> drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c: In function
> ‘gfx_v8_0_ring_emit_ce_meta_init’:
> drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c:7263:2: warning: missing braces
Since commit 2d984ad132a8 ("PM / QoS: Introcuce latency tolerance device
PM QoS type") we reassign "c" to point at qos->latency_tolerance before
freeing c->notifiers, but the notifiers field of latency_tolerance is
never used.
Restore the original behaviour of freeing the notifiers pointer on
qos-
Hello,
On 02/16/2017 02:06 PM, Javier Martinez Canillas wrote:
> After commit 66d228a2bf03 ("regulator: core: Don't use regulators as
> supplies until the parent is bound"), input supplies aren't resolved
> if the input supplies parent device has not been bound. This prevent
> regulators to hold a
Hi!
> > > 4.10-rc4 broken
> > > 4.10-rc3 ok
> >
> > Hmm. If those actually end up being reliable, then there's not a whole
> > lot in between them wrt PCI or USB.
> >
> > What looked like the most likely candidate seems to be xhci-specific,
> > though.
> >
> > But maybe it's something that isn
Hi Peter,
[auto build test WARNING on char-misc/char-misc-testing]
[also build test WARNING on v4.10-rc8 next-20170216]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Peter-Huewe/Fix-whole
When going to suspend, the I2C registers may be lost because the power to
VDDcore is cut. Restore them when resuming.
Signed-off-by: Alexandre Belloni
---
Changes in v2:
- don't cache unecessary registers and simply call at91_init_twi_bus()
drivers/i2c/busses/i2c-at91.c | 3 +++
1 file change
On 02/16, Chao Yu wrote:
> On 2017/2/16 9:16, Jaegeuk Kim wrote:
> > On 02/14, Jaegeuk Kim wrote:
> >> On 02/15, Chao Yu wrote:
> >>> On 2017/2/15 2:03, Jaegeuk Kim wrote:
> VFS uses f2fs_lookup() to decide f2fs_add_link() call during file
> creation.
> But, if there is a race condi
After commit 66d228a2bf03 ("regulator: core: Don't use regulators as
supplies until the parent is bound"), input supplies aren't resolved
if the input supplies parent device has not been bound. This prevent
regulators to hold an invalid reference if its supply parent device
driver probe is deferred
On Thu, Feb 16, 2017 at 10:50 AM, wrote:
>
>
> Hi Alan,
>
> On Wed, 15 Feb 2017, Alan Tull wrote:
>
>> Currently if a user applies > 1 overlays to a region
>> and removes them, we get a slow warning from devm_kfree.
>> because the pointer to the FPGA image info was overwritten.
>>
>> This commit
Hi Matthew,
On Wed, Feb 15, 2017 at 1:10 PM, wrote:
> +static int alt_pr_fpga_write_complete(struct fpga_manager *mgr,
> + struct fpga_image_info *info)
> +{
> + u32 i;
> +
> + for (i = 0; i < info->config_complete_timeout_us; i++) {
> +
On 02/16/2017 03:34 AM, Byungchul Park wrote:
> pick_next_pushable_dl_task(rq) has BUG_ON(rq->cpu != task_cpu(task))
> when it returns a task other than NULL, which means that task_cpu(task)
> must be rq->cpu. So if task == next_task, then task_cpu(next_task) must
> be rq->cpu as well. Remove the r
On 02/16/2017 03:34 AM, Byungchul Park wrote:
> pick_next_pushable_task(rq) has BUG_ON(rq_cpu != task_cpu(task)) when
> it returns a task other than NULL, which means that task_cpu(task) must
> be rq->cpu. So if task == next_task, then task_cpu(next_task) must be
> rq->cpu as well. Remove the redun
This adds a device property for setting the configuration for the
HAP_ACT register field so that the connected actuator type can be
configured on systems that are not using pdata.
Signed-off-by: Richard Fitzgerald
---
Documentation/devicetree/bindings/input/arizona-haptics.txt | 10 ++
M
On Tue, Feb 14, 2017 at 11:36:07AM -0800, Shaohua Li wrote:
> There are a few places the code assumes anonymous pages should have
> SwapBacked flag set. MADV_FREE pages are anonymous pages but we are
> going to add them to LRU_INACTIVE_FILE list and clear SwapBacked flag
> for them. The assumption
One thing overlooked by commit 9cc46516ddf4 ("userns: Add a knob to
disable setgroups on a per user namespace basis") is that because
setgroups(2) no longer works in user namespaces it doesn't make any
sense to be returning weird group IDs that the process cannot do
anything with.
This change, alo
On Wed, Feb 15, 2017 at 6:16 PM, Moritz Fischer
wrote:
> On Wed, Feb 15, 2017 at 2:42 PM, Alan Tull wrote:
>> On Wed, Feb 15, 2017 at 3:36 PM, Moritz Fischer
>> wrote:
>>> Jason,
>>>
>>> On Wed, Feb 15, 2017 at 1:15 PM, Jason Gunthorpe
>>> wrote:
On Wed, Feb 15, 2017 at 12:54:27PM -0800, M
2017-02-13 10:22 GMT+01:00 Sekhar Nori :
> Hi Bartosz,
>
> On Tuesday 07 February 2017 10:11 PM, Bartosz Golaszewski wrote:
>> The following series adds support for v4l2 display on da850-evm with
>> a UI board in device tree boot mode.
>>
>> Patches 1/10 - 5/10 deal with the device tree: we fix whi
The Lenovo Thinkpads use RMI4 over SMBus in addition to PS/2 for their
trackpad. The problem is that the device doesn't enumerate itself besides
some registers in PS/2.
Once the initial PS/2 initialization has been made, we need a way to unbind
psmouse from the touchpad and use a different (dummy)
This driver is a glue between PS/2 devices that enumerate
the RMI4 devices and Elan touchpads to the RMI4 (or Elan)
SMBus driver.
We use an intermediate platform device to not add a
dependency between psmouse and I2C. It also handles
the subtleties of going around the serio mutex lock by
deferring
301 - 400 of 854 matches
Mail list logo
