2017-08-24 12:21 GMT+08:00 Wanpeng Li :
> From: Wanpeng Li
>
> vmx_complete_interrupts() assumes that the exception is always injected,
> so it would be dropped by kvm_clear_exception_queue(). This patch separates
> exception.pending from exception.injected, exception.inject represents the
> excep
Hello,
Le 23/08/2017 à 18:46, Florian Fainelli a écrit :
> On 08/23/2017 01:50 AM, Romain Perier wrote:
>> This code is no longer used, the logging function was changed by commit
>> fbca164776e4 ("net: stmmac: Use the right logging functi"). It was
>> previously showing information about the type
Add support for GD25Q256, a 32MiB SPI Nor flash
from GigaDevice.
Signed-off-by: Andy Yan
---
Changes in v6: None
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in v2: None
drivers/mtd/spi-nor/spi-nor.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/mtd
Some manufacturers may use different bit to set QE on
different memories.
The GD25Q256 from GigaDevice is a example, which uses S6(bit 6
of the Status Register-1) to set QE, which is different with
other supported memories from GigaDevice that use S9(bit 1 of
the Status Register-2). This makes it
On 08/24/2017 08:25 AM, Yang, Wenyou wrote:
>
>
> On 2017/8/23 18:37, Hans Verkuil wrote:
>> On 08/22/17 09:30, wenyou.y...@microchip.com wrote:
>>> Hi Hans,
>>>
-Original Message-
From: Hans Verkuil [mailto:hverk...@xs4all.nl]
Sent: 2017年8月22日 15:00
To: Wenyou Yang -
Implement vas_init() and vas_exit() functions for a new VAS module.
This VAS module is essentially a library for other device drivers
and kernel users of the NX coprocessors like NX-842 and NX-GZIP.
In the future this will be extended to add support for user space
to access the NX coprocessors.
VA
Move the GET_FIELD and SET_FIELD macros to vas.h as VAS and other
users of VAS, including NX-842 can use those macros.
There is a lot of related code between the VAS/NX kernel drivers
and skiboot. For consistency, switch the order of parameters in
SET_FIELD to match the order in skiboot.
Signed-o
Define helpers to initialize window context registers of the VAS
hardware. These will be used in follow-on patches when opening/closing
VAS windows.
Signed-off-by: Sukadev Bhattiprolu
---
Changelog[v6]
- Add support for FTW windows and drop the fault window id
code since it is n
Define the vas_rx_win_open() interface. This interface is intended to be
used by the Nest Accelerator (NX) driver(s) to setup receive windows for
one or more NX engines (which implement compression/encryption algorithms
in the hardware).
Follow-on patches will provide an interface to close the win
Define interfaces (wrappers) to the 'copy' and 'paste' instructions
(which are new in PowerISA 3.0). These are intended to be used to
by NX driver(s) to submit Coprocessor Request Blocks (CRBs) to the
NX hardware engines.
Signed-off-by: Sukadev Bhattiprolu
---
Changelog[v4]
- Export symb
Define an interface to open a VAS send window. This interface is
intended to be used the Nest Accelerator (NX) driver(s) to open
a send window and use it to submit compression/encryption requests
to a VAS receive window.
The receive window, identified by the [vasid, cop] parameters, must
already b
Define an interface to return a system-wide unique id for a given VAS
window.
The vas_win_id() will be used in a follow-on patch to generate an unique
handle for a user space receive window. Applications can use this handle
to pair send and receive windows for fast thread-wakeup.
The hardware ref
Define the vas_win_close() interface which should be used to close a
send or receive windows.
While the hardware configurations required to open send and receive windows
differ, the configuration to close a window is the same for both. So we use
a single interface to close the window.
Signed-off-
Define an interface that the NX drivers can use to find the physical
paste address of a send window. This interface is expected to be used
with the mmap() operation of the NX driver's device. i.e the user space
process can use driver's mmap() operation to map the send window's paste
address into th
Define helpers to allocate/free VAS window objects. These will
be used in follow-on patches when opening/closing windows.
Signed-off-by: Sukadev Bhattiprolu
---
arch/powerpc/platforms/powernv/vas-window.c | 70 +
1 file changed, 70 insertions(+)
diff --git a/arch/pow
Define macros for the VAS hardware registers and bit-fields as well
as couple of data structures needed by the VAS driver.
Signed-off-by: Sukadev Bhattiprolu
---
Changelog[v7]
- Move the threshold control macros from uapi/asm/vas.h to
asm/vas.h for now. When we actually have an
Define some helper functions to access the MMIO regions. We use these
in follow-on patches to read/write VAS hardware registers. They are
also used to later issue 'paste' instructions to submit requests to
the NX hardware engines.
Signed-off-by: Sukadev Bhattiprolu
---
Changelog [v6]:
- M
Power9 introduces a hardware subsystem referred to as the Virtual
Accelerator Switchboard (VAS). VAS allows kernel subsystems and user
space processes to directly access the Nest Accelerator (NX) engines
which implement compression and encryption algorithms in the hardware.
NX has been in Power pr
From: Joonsoo Kim
0. History
This patchset is the follow-up of the discussion about the
"Introduce ZONE_CMA (v7)" [1]. Please reference it if more information
is needed.
1. What does this patch do?
This patch changes the management way for the memory of the CMA area
in the MM subsystem. Curren
From: Joonsoo Kim
Now, all reserved pages for CMA region are belong to the ZONE_MOVABLE
and it only serves for a request with GFP_HIGHMEM && GFP_MOVABLE.
Therefore, we don't need to maintain ALLOC_CMA at all.
Reviewed-by: Aneesh Kumar K.V
Acked-by: Vlastimil Babka
Signed-off-by: Joonsoo Kim
-
From: Joonsoo Kim
CMA area is now managed by the separate zone, ZONE_MOVABLE,
to fix many MM related problems. In this implementation, if
CONFIG_HIGHMEM = y, then ZONE_MOVABLE is considered as HIGHMEM and
the memory of the CMA area is also considered as HIGHMEM.
That means that they are considere
From: Joonsoo Kim
This patchset is the follow-up of the discussion about the
"Introduce ZONE_CMA (v7)" [1]. Please reference it if more information
is needed.
In this patchset, the memory of the CMA area is managed by using
the ZONE_MOVABLE. Since there is another type of the memory in this zone
On Mon, Aug 14 2017, NeilBrown wrote:
> On Fri, Aug 11 2017, Trond Myklebust wrote:
>
>> On Fri, 2017-08-11 at 14:31 +1000, NeilBrown wrote:
>>> Funny story. 4.5 years ago we discarded the FS_REVAL_DOT superblock
>>> flag and introduced the d_weak_revalidate dentry operation instead.
>>> We duly
This adds support for reading and writing date/time from/to ds1341 chip.
ds1341 chip has other features - alarms, input clock (can be used instead
of intercal oscillator for better accuracy), output clock ("square wave
generation"). However, not all of that is available at the same time.
Same chip
On 2017/8/23 18:37, Hans Verkuil wrote:
On 08/22/17 09:30, wenyou.y...@microchip.com wrote:
Hi Hans,
-Original Message-
From: Hans Verkuil [mailto:hverk...@xs4all.nl]
Sent: 2017年8月22日 15:00
To: Wenyou Yang - A41535 ; Mauro Carvalho
Chehab
Cc: Nicolas Ferre - M43238 ; linux-
ker...@v
snd_ac97_res_table are not supposed to change at runtime. All functions
working with snd_ac97_res_table provided by work with
const snd_ac97_res_table. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
sound/pci/nm256/nm256.c | 2 +-
1 file changed, 1 insertion(+), 1 delet
在 2017-08-24 14:07，Maxime Ripard 写道：
On Wed, Aug 23, 2017 at 11:13:04PM +0800, icen...@aosc.io wrote:
在 2017-08-23 22:35，Maxime Ripard 写道：
> On Wed, Aug 23, 2017 at 07:56:29PM +0800, icen...@aosc.io wrote:
> > > > + reg = <0x01c0f000 0x1000>;
> > > > + clocks
Hi Yong,
[auto build test WARNING on iommu/next]
[also build test WARNING on next-20170823]
[cannot apply to v4.13-rc6]
[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/Yong-Wu/MT2712-IOMMU
Hello,
after reading the NFS(5) manpage and doing some searching through the
mailing list archive (of course, due to it being ubiquitous in posted
logs, searching for "addr" and "clientaddr" was a bit hopeless) I have
come to conclude that NFS does not have an option for explicitly
specifying
On Wed, Aug 23, 2017 at 07:47:14PM +0200, Peter Zijlstra wrote:
> Those are fine and are indeed the flush_work() vs work inversion.
>
> The two straight forward annotations are:
>
> flush_work(work) process_one_work(wq, work)
> A(work) A(work)
> R(work) work->
On 24/08/17 00:27, Boris Ostrovsky wrote:
> Commit aba831a69632 ("xen: remove tests for pvh mode in pure pv paths")
> removed XENFEAT_auto_translated_physmap test in xen_alloc_p2m_entry()
> since it is assumed that the routine is never called by non-PV guests.
>
> However, alloc_xenballooned_pages
On 08/20, icen...@aosc.io wrote:
>在 2017-08-20 08:59，kbuild test robot 写道：
>>Hi Chen-Yu,
>>
>>[auto build test ERROR on robh/for-next]
>>[also build test ERROR on v4.13-rc5 next-20170817]
>>[if your patch is applied to the wrong git tree, please drop us a note
>>to help improve the system]
>
>In fa
On Wed, Aug 23, 2017 at 11:13:04PM +0800, icen...@aosc.io wrote:
> 在 2017-08-23 22:35，Maxime Ripard 写道：
> > On Wed, Aug 23, 2017 at 07:56:29PM +0800, icen...@aosc.io wrote:
> > > > > + reg = <0x01c0f000 0x1000>;
> > > > > + clocks = <&ccu CLK_BUS_MMC0>, <&ccu
On Tue, 2017-08-22 at 10:37 +0300, Luca Coelho wrote:
> From: Luca Coelho
>
> Work queues cannot be allocated when a mutex is held because the mutex
> may be in use and that would make it sleep. Doing so generates the
> following splat with 4.13+:
>
> [ 19.513298]
Check memory allocation failure and return -ENOMEM in such a case.
Signed-off-by: Christophe JAILLET
---
drivers/media/i2c/smiapp/smiapp-core.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/media/i2c/smiapp/smiapp-core.c
b/drivers/media/i2c/smiapp/smiapp-core.c
index aff55e1dffe
Hi all,
[Just adding Dick and James to the cc list]
On Thu, 24 Aug 2017 15:57:56 +1000 Stephen Rothwell
wrote:
>
> After merging the scsi-mkp tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> drivers/scsi/lpfc/lpfc_nvmet.c:1457:1: warning:
> 'lpfc_nvmet_rep
Hi Martin,
After merging the scsi-mkp tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:
drivers/scsi/lpfc/lpfc_nvmet.c:1457:1: warning: 'lpfc_nvmet_replenish_context'
defined but not used [-Wunused-function]
lpfc_nvmet_replenish_context(struct lpfc_hba *phba,
^
I
On 23.8.2017 12:55, Shubhrajyoti Datta wrote:
> Signed-off-by: Shubhrajyoti Datta
Empty commit message?
What's the reason for this change?
M
> ---
> drivers/tty/serial/xilinx_uartps.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/tty/serial/xilinx_uartps.c
On 2017-08-21 12:34, Pierre Yves MORDRET wrote:
> OK. I will redesign my driver to take into account this idea.
>
> I believe I should get rid of my custom API in DMA for channelID as well.
> Please
> confirm. Not very clear for me whether I can keep it or not.
Yes, you should be able to get r
'min_vruntime_copy' is copied when 'min_vruntime' is updated for cfq_rq
and used to check if updating 'min_vruntime' is completed on reader side.
Because 'min_vruntime' variable is 64bit, we need a mimic of seqlock to
check if the variable is not being updated on 32bit machines.
On 64BIT_ATOMIC
On some 32-bit architectures, 64bit accesses are atomic when certain
conditions are satisfied.
For example, on LPAE (Large Physical Address Extension) enabled ARM
architecture, 'ldrd/strd' (load/store doublewords) instructions are 64bit
atomic as long as the address is 64-bit aligned. This featu
On some 32-bit architectures, 64bit accesses are atomic when certain
conditions are satisfied.
For example, on LPAE (Large Physical Address Extension) enabled ARM
architecture, 'ldrd/strd' (load/store doublewords) instructions are 64bit
atomic as long as the address is 64-bit aligned. This featur
'ldrd/strd' (load/store doublewords) instructions are 64bit atomic as
long as the address is 64-bit aligned on LPAE (Large Physical Address
Extension) enabled architectures. This feature is to guarantee atomic
accesses on newly introduced 64bit wide descriptors in the translation
tables.
Making
From: Joonsoo Kim
Freepage on ZONE_HIGHMEM doesn't work for kernel memory so it's not that
important to reserve. When ZONE_MOVABLE is used, this problem would
theorectically cause to decrease usable memory for GFP_HIGHUSER_MOVABLE
allocation request which is mainly used for page cache and anon pa
From: Colin King
Date: Wed, 23 Aug 2017 12:59:48 +0100
> From: Colin Ian King
>
> iph is being assigned the same value twice; remove the redundant
> first assignment. (Thanks to Nikolay Aleksandrov for pointing out
> that the first asssignment should be removed and not the second)
>
> Fixes wa
From: Stefano Brivio
Date: Wed, 23 Aug 2017 13:27:13 +0200
> inet_diag_msg_sctp{,l}addr_fill() and sctp_get_sctp_info() copy
> sizeof(sockaddr_storage) bytes to fill in sockaddr structs used
> to export diagnostic information to userspace.
>
> However, the memory allocated to store sockaddr info
From: Arvind Yadav
Date: Wed, 23 Aug 2017 16:22:20 +0530
> genl_ops are not supposed to change at runtime. All functions
> working with genl_ops provided by work with
> const genl_ops. So mark the non-const structs as const.
>
> Signed-off-by: Arvind Yadav
Applied.
From: Andrew Lunn
Date: Wed, 23 Aug 2017 14:45:56 +0200
> On Wed, Aug 23, 2017 at 03:46:56PM +0530, Arvind Yadav wrote:
>> dsa_switch_ops are not supposed to change at runtime. All functions
>> working with dsa_switch_ops provided by work with
>> const dsa_switch_ops. So mark the non-const struc
The commit ("iommu/mediatek: Enlarge the validate PA range
for 4GB mode") introduce the following build error:
drivers/iommu/mtk_iommu.c: In function 'mtk_iommu_hw_init':
>> drivers/iommu/mtk_iommu.c:536:30: error: 'const struct mtk_iommu_data'
has no member named 'm4u_type'; did you mean 'm4u
Hi Greg,
On Tue, 22 Aug 2017 15:07:33 +1000 Stephen Rothwell
wrote:
>
> Hi Kishon,
>
> After merging the phy-next tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> drivers/phy/ralink/phy-ralink-usb.c: In function 'ralink_usb_phy_probe':
> drivers/phy/ralink/phy-
From: Colin King
Date: Wed, 23 Aug 2017 10:59:40 +0100
> From: Colin Ian King
>
> The functions set_ctrl0 and set_ctrl1 are local to the source and do
> not need to be in global scope, so make them static.
>
> Cleans up sparse warnings:
> symbol 'set_ctrl0' was not declared. Should it be stati
I found an ACPI cache leak in ACPI early termination and boot continuing case.
When early termination is occurred due to malicious ACPI table, Linux kernel
terminates ACPI function and continues to boot process. While kernel terminates
ACPI function, kmem_cache_destroy() reports Acpi-Operand cache
On Wed, Aug 23, 2017 at 12:26:52PM +0200, Peter Zijlstra wrote:
> On Wed, Aug 23, 2017 at 11:43:23AM +0900, Byungchul Park wrote:
> > On Tue, Aug 22, 2017 at 03:49:22PM +0200, Peter Zijlstra wrote:
>
> > > So I think we'll end up hitting a lockdep deficiency and not trigger the
> > > splat on flus
On Wed, Aug 23, 2017 at 12:46:48PM +0200, Peter Zijlstra wrote:
> On Wed, Aug 23, 2017 at 11:31:18AM +0900, Byungchul Park wrote:
> > On Tue, Aug 22, 2017 at 11:06:03AM +0200, Peter Zijlstra wrote:
>
> > Currently, we do the following in process_one_work(),
> >
> > lockdep_map_acquire for a workq
PERST must be asserted around ~500ms before the reboot is applied.
During soft reset (e.g., "reboot" from Linux) on some iproc based SOCs
LCPLL clock and PERST both goes off simultaneously.
This will cause certain Endpoints Intel NVMe not get detected, upon
next boot sequence.
This is specificall
This patch factors out ep configuration access
as a separate function.
Signed-off-by: Oza Pawandeep
diff --git a/drivers/pci/host/pcie-iproc.c b/drivers/pci/host/pcie-iproc.c
index c574863..61d9be6 100644
--- a/drivers/pci/host/pcie-iproc.c
+++ b/drivers/pci/host/pcie-iproc.c
@@ -448,6 +448,31 @
PCIe spec r3.1, sec 2.3.2
If CRS software visibility is not enabled, the RC must reissue the
config request as a new request.
- If CRS software visibility is enabled,
- for a config read of Vendor ID, the RC must return 0x0001 data
- for all other config reads/writes, the RC must reissue the
req
PCI: iproc: Retry request when CRS returned from EP Above patch adds
support for CRS in PCI RC driver, otherwise if not handled at lower
level, the user space PMD (poll mode drivers) can timeout.
PCI: iproc: add device shutdown for PCI RC This fixes the issue where
certian PCI endpoints are not ge
On Tue 18 Jul 23:39 PDT 2017, fengl...@codeaurora.org wrote:
> From: Fenglin Wu
>
> Power source selection in DIG_VIN_CTL is indexed from 0, in the range
> check it shouldn't be equal to the total number of power sources.
>
Acked-by: Bjorn Andersson
Regards,
Bjorn
> Signed-off-by: Fenglin W
On 24/08/17 12:07, NeilBrown wrote:
>
>
> The more precise details, that automount action for indirect automount
> points is not triggered when the 'browse' option is used, is probably
> not necessary.
>
> Ian: if you agree with that text, and Michael doesn't provide alternate
> evidence, I'll s
Add support for optional cdn dp codec.
Signed-off-by: Jeffy Chen
---
Changes in v7: None
Changes in v6: None
Changes in v3: None
Changes in v2: None
sound/soc/rockchip/Kconfig| 1 +
sound/soc/rockchip/rk3399_gru_sound.c | 59 +--
2 files changed, 58
Update description for newly added optional audio codecs.
Signed-off-by: Jeffy Chen
Acked-by: Rob Herring
---
Changes in v7: None
Changes in v6: None
Changes in v3: None
Changes in v2: None
Documentation/devicetree/bindings/sound/rockchip,rk3399-gru-sound.txt | 2 +-
1 file changed, 1 inserti
Refactor rockchip_sound_probe, parse dai links from dts instead of
hard coding them.
Signed-off-by: Jeffy Chen
Reviewed-by: Matthias Kaehlcke
Tested-by: Matthias Kaehlcke
---
Changes in v7: None
Changes in v6: None
Changes in v3:
Use compatible to match audio codecs
-- Suggested-by Mat
Currently we are using a fixed list of dai links in the driver.
This serial of patches would let the driver parse dai links from
dts, so that we can make some of them optional for future boards.
Tested on my chromebook bob(with cros 4.4 kernel), it still works
after disabled rt5514 codecs in the
Add support for optional dmic codec.
Signed-off-by: Jeffy Chen
---
Changes in v7: None
Changes in v6:
Add dmic wakeup delay(not used for now).
Changes in v3: None
Changes in v2: None
sound/soc/rockchip/Kconfig| 1 +
sound/soc/rockchip/rk3399_gru_sound.c | 36 +
Currently we are using codec name for rt5514 dsp dai link, use codec
of_node instead.
Signed-off-by: Jeffy Chen
---
Changes in v7:
Rebase on the newest for-next
Changes in v6: None
Changes in v3: None
Changes in v2: None
sound/soc/rockchip/rk3399_gru_sound.c | 34 ++---
Add rt5514 dsp of_node to codec list for Gru boards.
Signed-off-by: Jeffy Chen
---
Changes in v7: None
Changes in v6: None
Changes in v3: None
Changes in v2: None
arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm64/boot/
Currently the rt5514 i2c driver and rt5514 spi driver are using the same
compatible string.
Add additional unused compatible strings to identify them for Gru
boards.
Signed-off-by: Jeffy Chen
---
Changes in v7: None
Changes in v6: None
Changes in v3: None
Changes in v2: None
arch/arm64/boot/d
Hi,
On (08/24/17 12:39), Boqun Feng wrote:
> On Wed, Aug 23, 2017 at 02:55:17PM +0900, Sergey Senozhatsky wrote:
> > On (08/23/17 13:35), Boqun Feng wrote:
> > > > KERN_CONT and "\n" should not be together. "\n" flushes the cont
> > > > buffer immediately.
> > > >
> > >
> > > Hmm.. Not quite fam
On 24/08/17 12:07, NeilBrown wrote:
> On Wed, Aug 23 2017, Ian Kent wrote:
>
>>
>> That inconsistency has bothered me for quite a while now.
>>
>> It was carried over from the autofs module behavior when automounting
>> support was added to the VFS. What's worse is it prevents the use of
>> the AT
Hi Dong,
Thanks for noticing, will send new patch soon :)
On 08/24/2017 11:46 AM, Donglin Peng wrote:
On Thu, Aug 24, 2017 at 11:34 AM, Jeffy Chen wrote:
list_for_each_entry(dai, &component->dai_list, list) {
if (dlc->dai_name && strcmp(dai->name, dlc
On Wed, Aug 23, 2017 at 11:30 PM, Bjorn Helgaas wrote:
> On Wed, Aug 23, 2017 at 09:32:06PM +0530, Oza Oza wrote:
>> On Wed, Aug 23, 2017 at 9:22 PM, Sinan Kaya wrote:
>> > Hi Oza,
>> >
>> >> In working Enumuration case I get following:
>> >> [9.125976] pci :00:00.0: bridge configuration
The dai driver's name is allowed to be NULL. So add a sanity check for
that.
Signed-off-by: Jeffy Chen
Reported-by: Donglin Peng
---
Changes in v3:
Fix typo
Changes in v2:
Keep the oringinal check style.
sound/soc/soc-core.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
On Wed, Aug 23, 2017 at 02:55:17PM +0900, Sergey Senozhatsky wrote:
> On (08/23/17 13:35), Boqun Feng wrote:
> > > KERN_CONT and "\n" should not be together. "\n" flushes the cont
> > > buffer immediately.
> > >
> >
> > Hmm.. Not quite familiar with printk() stuffs, but I could see several
> > us
On Aug 23 2017 23:51, Oleksandr Grytsov wrote:
Hi,
Thank you for detailed explanation.
We understand that emulated interrupt on the frontend side is completely not
acceptable and definitely we need to provide some feedback mechanism from
Dom0 to DomU.
In our case it is technically impossible t
On 24/08/17 11:21, NeilBrown wrote:
> On Wed, Aug 23 2017, Ian Kent wrote:
>
>> On 23/08/17 10:32, Ian Kent wrote:
>>> On 23/08/17 09:06, NeilBrown wrote:
On Mon, Aug 21 2017, Ian Kent wrote:
>>
>> A mount isn't triggered by kern_path(pathname, 0, &path).
>> That '0' would ne
On Wed, Aug 23, 2017 at 10:20:02AM -0400, Zi Yan wrote:
> On 23 Aug 2017, at 3:49, Naoya Horiguchi wrote:
>
> > On Mon, Aug 14, 2017 at 09:52:13PM -0400, Zi Yan wrote:
> >> From: Zi Yan
> >>
> >> The loop in madvise_inject_error() reads its step size from a page
> >> after it is soft-offlined. It
Hello Sergey,
On Thu, Aug 24, 2017 at 10:49:36AM +0900, Sergey Senozhatsky wrote:
> Add ZSTD to the list of supported compression algorithms.
>
> Official benchmarks [1]:
First of all, thanks for the work!
I want to ask one thing.
Could you add some benchmark(e.g.,) result(comp ratio and speed
2017-08-23 20:27 GMT+08:00 Paolo Bonzini :
> On 23/08/2017 12:23, Wanpeng Li wrote:
>> @@ -6341,7 +6345,8 @@ static int inject_pending_event(struct kvm_vcpu *vcpu,
>> bool req_int_win)
>> int r;
>>
>> /* try to reinject previous events if any */
>> - if (vcpu->arch.exception.pendin
From: Sandeep Singh
The following commit cause a regression on ATI chipsets.
'commit e788787ef4f9 ("usb:xhci:Add quirk for Certain
failing HP keyboard on reset after resume")'
This causes pinfo->smbus_dev to be wrongly set to NULL on
systems with the ATI chipset that this function checks for fir
- Original Message -
> From: "Steven Rostedt"
> To: "Chunyu Hu"
> Cc: mi...@kernel.org, linux-kernel@vger.kernel.org
> Sent: Thursday, August 24, 2017 10:15:41 AM
> Subject: Re: [PATCH 2/2] tracing: Fix kmemleak in set_trigger_filter
>
> On Wed, 23 Aug 2017 18:58:03 -0400 (EDT)
> Chuny
Hi
On 2017-08-23, Eric W. Biederman wrote:
> Linus Torvalds writes:
> > On Wed, Aug 23, 2017 at 6:49 PM, Linus Torvalds
> > wrote:
[...]
> This is so far untested (except for compiling) but I think this will
> work.
>
> I factor out devpts_ptmx_path out of devpts_acquire so the code
> doesn'
From: Wanpeng Li
vmx_complete_interrupts() assumes that the exception is always injected,
so it would be dropped by kvm_clear_exception_queue(). This patch separates
exception.pending from exception.injected, exception.inject represents the
exception is injected or the exception should be rein
From: Wanpeng Li
[ cut here ]
WARNING: CPU: 7 PID: 3861 at /home/kernel/ssd/kvm/arch/x86/kvm//vmx.c:11299
nested_vmx_vmexit+0x176e/0x1980 [kvm_intel]
CPU: 7 PID: 3861 Comm: qemu-system-x86 Tainted: GW OE 4.13.0-rc4+ #11
RIP: 0010:nested_vmx_vmexit+0x176e/0x1980
From: Wanpeng Li
Use kvm_event_needs_reinjection() encapsulation.
Cc: Paolo Bonzini
Cc: Radim Krčmář
Signed-off-by: Wanpeng Li
---
arch/x86/kvm/vmx.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index dd710d3..c5f43ab 100644
-
From: Wanpeng Li
Move the nested_vmx_inject_exception_vmexit call from
nested_vmx_check_exception
to vmx_queue_exception.
Signed-off-by: Wanpeng Li
---
arch/x86/kvm/vmx.c | 21 +++--
1 file changed, 11 insertions(+), 10 deletions(-)
diff --git a/arch/x86/kvm/vmx.c b/arch/x8
On Wed, Aug 23 2017, Ian Kent wrote:
>
> That inconsistency has bothered me for quite a while now.
>
> It was carried over from the autofs module behavior when automounting
> support was added to the VFS. What's worse is it prevents the use of
> the AT_NO_AUTOMOUNT flag from working properly with
Dear all,
On 2017년 08월 24일 10:42, Chanwoo Choi wrote:
> The devfreq uses the OPP interface as a mandatory method
> and so the devfreq has to support the OPP notifier in order to
> catch the OPP events. So, this patch adds the new opp_notifier_cb()
> function pointer in the struct devfreq_dev_profi
Hi Rafael, Zheng,
At 07/31/2017 06:50 PM, Dou Liyang wrote:
Hi,
At 07/14/2017 01:52 PM, Dou Liyang wrote:
Linux uses acpi_early_init() to put the ACPI table management into
the late stage from the early stage where the mapped ACPI tables is
temporary and should be unmapped.
But, now initializ
On Thu, Aug 24, 2017 at 11:34 AM, Jeffy Chen wrote:
> list_for_each_entry(dai, &component->dai_list, list) {
> if (dlc->dai_name && strcmp(dai->name, dlc->dai_name)
> - && strcmp(dai->driver->name, dlc->dai_name))
> +
The dai driver's name is allowed to be NULL. So add a sanity check for
that.
Signed-off-by: Jeffy Chen
Reported-by: Donglin Peng
---
Changes in v2:
Keep the oringinal check style.
sound/soc/soc-core.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/sound/soc/soc-core.c b
bdev with a gendisk pointer and partitions
> index")
>
> interacting with commit
>
> c775d2098d35 ("bio-integrity: Fix regression if profile verify_fn is NULL")
>
> from Linus' tree (before v4.13-rc5).
>
> This should have been fixed up in commit
>
profile verify_fn is NULL")
from Linus' tree (before v4.13-rc5).
This should have been fixed up in commit
3b8848b41130 ("Merge branch 'master' into for-next")
I have used the block tree from next-20170823 for today.
--
Cheers,
Stephen Rothwell
Hi Mark,
On 08/23/2017 07:06 PM, Mark Brown wrote:
On Wed, Aug 23, 2017 at 07:42:55AM +0800, jeffy wrote:
>i think the original check is allowing NULL dlc dai_name to be a match...
>so we basically did:
>reject when dlc dai_name is valid, but not match the dai name
So it is, but this still lo
From: Stephan Gatzka
Date: Tue, 22 Aug 2017 14:25:07 +0200
> When using MII/GMII/SGMII in the Altera SoC, the phy needs to be
> wired through the FPGA. To ensure correct behavior, the appropriate
> bit in the System Manager FPGA Interface Group register needs to be
> set.
>
> Signed-off-by: Step
On Wed, Aug 23, 2017 at 8:11 PM, Eric W. Biederman
wrote:
> -static int pty_get_peer(struct tty_struct *tty, int flags)
> +int ptm_open_peer(struct file *master, struct tty_struct *tty, int flags)
> {
> int fd = -1;
> struct file *filp = NULL;
> int retval = -EINVAL;
> +
Hi Andy,
Le 23/08/2017 à 12:01, Andy Yan a écrit :
> Add support for GD25Q256, a 32MiB SPI Nor
> flash from GigaDevice.
>
> The GD25Q256 uses S6 to set QE, which is
> different with other supported memories
> from GigaDevice that use S9. So we introduce
> a quad_enable function which can be set p
On Wed, Aug 23 2017, Ian Kent wrote:
> On 23/08/17 10:32, Ian Kent wrote:
>> On 23/08/17 09:06, NeilBrown wrote:
>>> On Mon, Aug 21 2017, Ian Kent wrote:
>>>
>
> A mount isn't triggered by kern_path(pathname, 0, &path).
> That '0' would need to include one of
> LOOKUP_PARENT | LO
Linus Torvalds writes:
> On Wed, Aug 23, 2017 at 6:49 PM, Linus Torvalds
> wrote:
>>
>> Argh. And it's *not* fairly straightforward, because the
>> tty_operations "ioctl()" function pointer only gets 'struct tty *'.
>>
>> So in the TIOCGPTPEER path, we don't actually have access to the file
>> p
On Mon, Aug 21, 2017 at 02:09:31AM +0200, Mickaël Salaün wrote:
> Add a basic sandbox tool to create a process isolated from some part of
> the system. This sandbox create a read-only environment. It is only
> allowed to write to a character device such as a TTY:
>
> # :> X
> # echo $?
> 0
>
1 - 100 of 847 matches
Mail list logo
