On 03/21/2018 06:28 PM, jgli...@redhat.com wrote:
> From: Ralph Campbell
>
> The hmm_mirror_register() function registers a callback for when
> the CPU pagetable is modified. Normally, the device driver will
> call hmm_mirror_unregister() when the process using the device is
> finished. However,
Hi Dan,
Today's linux-next merge of the nvdimm tree got a conflict in:
fs/xfs/xfs_inode.h
between commit:
f5c54717bf2b ("xfs: remove xfs_zero_range")
from the xfs tree and commit:
6ea4108852e9 ("xfs: prepare xfs_break_layouts() for another layout type")
from the nvdimm tree.
I fixed i
Hi Philippe,
> Actually to be consistent if you want to use GPL-2-0 (and not "or
> later") you should use:
>
> 1. at the top, for a c. file:
> // SPDX-License-Identifier: GPL-2.0
>
> or for a .h file:
> /* SPDX-License-Identifier: GPL-2.0 */
>
> The doc explains it all. Including the comment st
On Wed, Mar 21, 2018 at 11:28 PM, Paul Kocialkowski
wrote:
> It turns out that the frontend is not capable of preserving the alpha
> component (that is always set to 0xff), so only support XRGB
> instead.
>
> Signed-off-by: Paul Kocialkowski
> ---
> drivers/gpu/drm/sun4i/sun4i_backend.c | 4
Hi Sinan,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.16-rc6 next-20180321]
[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
Hi all,
Today's linux-next merge of the drm tree got conflicts in several amdgpu
files because there are a set of (mostly identical) patches that appear
Linus' tree and the drm tree. In each case I just used the version fo
the file from the drm tree.
You should do a test merge between your tree
Hi Martin,
After merging the scsi-mkp tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
drivers/scsi/qla2xxx/qla_gs.c: In function 'qla24xx_async_gnnft_done':
drivers/scsi/qla2xxx/qla_gs.c:3974:7: error: 'fc4type' undeclared (first use in
this function); did you mean 'fc
On 2018.03.21 15:15 Rafael J. Wysocki wrote:
> On Wed, Mar 21, 2018 at 6:59 PM, Thomas Ilsche wrote:
>> On 2018-03-21 15:36, Rafael J. Wysocki wrote:
>>>
>>>
>>> So please disregard this one entirely and take the v7.2 replacement
>>> instead of it:https://patchwork.kernel.org/patch/10299429/
>>>
>>
On Wed, Mar 21, 2018 at 09:55:52AM -0700, Moritz Fischer wrote:
> On Wed, Mar 21, 2018 at 10:50:01AM +0800, Wu Hao wrote:
> > On Tue, Mar 20, 2018 at 03:32:34PM -0500, Alan Tull wrote:
> > > On Tue, Feb 13, 2018 at 3:24 AM, Wu Hao wrote:
> > >
> > > Hi Hao,
> > >
> > > Elsewhere we discussed mov
于 2018年3月22日 GMT+08:00 上午1:13:42, "Jernej Škrabec" 写到:
>Hi all,
>
>Dne sreda, 21. marec 2018 ob 03:18:13 CET je Icenowy Zheng napisal(a):
>> 于 2018年3月21日 GMT+08:00 上午2:46:46, Maxime Ripard
>
>写到:
>> >On Sat, Mar 17, 2018 at 01:53:49AM +0800, Icenowy Zheng wrote:
>> >> All the sub-blocks of Allw
On Thu, Mar 22, 2018 at 11:06:00AM +0800, Ji Zhang wrote:
> When we dump the backtrace of some specific task, there is a potential race
> condition due to the task may be running on other cores if SMP enabled.
> That is because for current implementation, if the task is not the current
> task, we w
Hi Martin,
Today's linux-next merge of the scsi-mkp tree got a conflict in:
drivers/scsi/qla2xxx/qla_os.c
between commit:
2b5b96473efc ("scsi: qla2xxx: Fix FC-NVMe LUN discovery")
from Linus' tree and commit:
33b28357dd00 ("scsi: qla2xxx: Fix Async GPN_FT for FCP and FC-NVMe scan")
fro
On Thursday 22 March 2018 07:08 AM, Mark Brown wrote:
On Wed, Mar 21, 2018 at 11:15:16AM +0530, Mukunda,Vijendar wrote:
There is a patch dependency .
Below patch not merged yet. We submitted for upstream review.
[PATCH V2] ASoC: dwc: I2S Controller instance param added
You need to mention de
There are some global registers in Spreadtrum sc27xx PMICs, which will
be accessed by other drivers. So this patch adds one syscon cell to
help to access the PMIC's global registers.
Signed-off-by: Baolin Wang
---
drivers/mfd/sprd-sc27xx-spi.c |3 +++
1 file changed, 3 insertions(+)
diff --
Hi Miquel,
Thanks for reviewing the patch series.
Please see my comments below.
> -Original Message-
> From: Miquel Raynal [mailto:miquel.ray...@bootlin.com]
> Sent: Tuesday, March 20, 2018 2:38 AM
> To: nagasureshkumarre...@gmail.com
> Cc: boris.brezil...@bootlin.com; rich...@nod.at; dw.
Hi, Kumar
On Thu, 2018-03-22 at 11:30 +0800, Viresh Kumar wrote:
> On 21-03-18, 18:21, Shunyong Yang wrote:
> >
> > When multiple cpus are related in one cpufreq policy, the first
> > online cpu
> > will be chosen by default to handle cpufreq operations. In a CPPC
> > case,
> > let's take two rel
When debugging recent kernels, people will see '(ptrval)' but there
isn't much information as to what that means. Briefly describe why it's
there.
Signed-off-by: Joel Stanley
---
Documentation/core-api/printk-formats.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Doc
On Friday 16 March 2018 01:27 PM, Ulf Hansson wrote:
> On 16 March 2018 at 05:20, Harish Jenny K N wrote:
>>
>> On Thursday 15 March 2018 05:59 PM, Ulf Hansson wrote:
>>> On 15 March 2018 at 11:26, Andy Shevchenko
>>> wrote:
On Thu, 2018-03-15 at 11:12 +0100, Ulf Hansson wrote:
> On 13
On Tue, Mar 13, 2018 at 05:55:35PM +0100, Pierre-Yves MORDRET wrote:
> The bitfield dma_inuse is allocated of size dma_requests bits, thus a
> valid bit address is from 0 to (dma_requests - 1).
> When find_first_zero_bit() fails, it returns dma_requests as invalid
> address.
> Using such address fo
On 3/21/18 10:12 PM, Srivatsa S. Bhat wrote:
> On 3/21/18 7:02 PM, Steve French wrote:
>> Found a patch which solves the dependency issue. In my testing (on
>> 4.9, with Windows 2016, and also to Samba) as Pavel suggested this
>> appears to fix the problem, but I will let Srivatsa confirm that it
On 3/21/18 7:02 PM, Steve French wrote:
> Found a patch which solves the dependency issue. In my testing (on
> 4.9, with Windows 2016, and also to Samba) as Pavel suggested this
> appears to fix the problem, but I will let Srivatsa confirm that it
> also fixes it for him. The two attached patches
On Wednesday 21 Mar 2018 at 15:54:58 (+), Patrick Bellasi wrote:
> On 21-Mar 14:26, Quentin Perret wrote:
> > On Wednesday 21 Mar 2018 at 12:39:21 (+), Patrick Bellasi wrote:
> > > On 20-Mar 09:43, Dietmar Eggemann wrote:
> > > > From: Quentin Perret
[...]
> > So actually, what I can do
On Wed, Mar 21, 2018 at 07:15:14PM +0300, Kirill Tkhai wrote:
> On 20.03.2018 17:34, Dave Chinner wrote:
> > On Tue, Mar 20, 2018 at 04:15:16PM +0300, Kirill Tkhai wrote:
> >> On 20.03.2018 03:18, Dave Chinner wrote:
> >>> On Mon, Mar 19, 2018 at 02:06:01PM +0300, Kirill Tkhai wrote:
> On 17.0
Hi Ji Zhang,
On Thu, Mar 22, 2018 at 11:06:00AM +0800, Ji Zhang wrote:
> When we dump the backtrace of some specific task, there is a potential race
> condition due to the task may be running on other cores if SMP enabled.
> That is because for current implementation, if the task is not the curren
When using vfio to pass through a PCIe device (e.g. a GPU card) that
has a huge BAR (e.g. 16GB), a lot of cycles are wasted on memory
pinning because PFNs of PCI BAR are not backed by struct page, and
the corresponding VMA has flag VM_PFNMAP.
With this change, when pinning a region which is a raw
Per the ACPI specification the only functional purpose for a DIMM
Control Region to be mapped into the system physical address space, from
an OSPM perspective, is to support block-apertures. However, there are
some BIOSen that publish DIMM Control Region SPA entries for pre-boot
environment consump
On Wed, Mar 21, 2018 at 06:50:54PM -0500, Alan Tull wrote:
> On Tue, Mar 20, 2018 at 2:10 AM, Wu Hao wrote:
>
> >> > +static int afu_mmap(struct file *filp, struct vm_area_struct *vma)
> >> > +{
> >> > + struct fpga_afu_region region;
> >> > + struct platform_device *pdev = filp->priv
On Wed, Mar 21, 2018 at 06:54:58PM -0500, Alan Tull wrote:
> On Tue, Feb 13, 2018 at 3:24 AM, Wu Hao wrote:
>
> Hi Hao,
>
> > +static int
> > +build_info_create_dev(struct build_feature_devs_info *binfo,
> > + enum fpga_id_type type, const char *name,
> > +
On Thu, 2018-03-22 at 13:37 +0900, y.k.oh wrote:
>
> On 03/14/2018 10:58 PM, Greg KH wrote:
> > On Wed, Mar 14, 2018 at 11:17:05AM +0900, YOUNGKEUN OH wrote:
> > > Cleanup checkpatch error:
> > > ERROR: Macros with complex values should be enclosed in parentheses
> > >
> > > Signed-off-by: YOUNGK
On Tue, Mar 20, 2018 at 12:04:44PM +0100, Benjamin Tissoires wrote:
> Hi,
>
> Patches 1 and 2 are related to the Razer Blade Stealth that has some dead zone
> near the edges of the touchpad.
> Patches 3 was previously sent and reviewed by Dmitry and he suggested patch 4
> at the time.
> Patches 5.
On 03/14/2018 10:58 PM, Greg KH wrote:
> On Wed, Mar 14, 2018 at 11:17:05AM +0900, YOUNGKEUN OH wrote:
>> Cleanup checkpatch error:
>> ERROR: Macros with complex values should be enclosed in parentheses
>>
>> Signed-off-by: YOUNGKEUN OH
>> ---
>> drivers/tty/serial/samsung.c | 16 --
On (03/21/18 15:49), Nick Terrell wrote:
> depends on CONFIG_CRYPTO_ZSTD, which isn't defined until this patch is in
Yikes! How come I missed that... :)
> [0]
> lkml.kernel.org/r/9c9416b2dff19f05fb4c35879aaa83d11ff72c92.1521626182.git.geliangt...@gmail.com
Signed-off-by: Nick Terrell ?
CC: Vaneet Narang.
On (03/21/18 10:10), Maninder Singh wrote:
> diff --git a/lib/lz4/lz4_compress.c b/lib/lz4/lz4_compress.c
> index cc7b6d4..185c358 100644
> --- a/lib/lz4/lz4_compress.c
> +++ b/lib/lz4/lz4_compress.c
> @@ -183,7 +183,8 @@ static FORCE_INLINE int LZ4_compress_generic(
>
Hi Randy,
Thanks for reviewing the patch.
I will address below mentioned comments in next version of patch.
Thanks,
Naga Sureshkumar Relli.
> -Original Message-
> From: Randy Dunlap [mailto:rdun...@infradead.org]
> Sent: Thursday, March 15, 2018 5:27 AM
> To: nagasureshkumarre...@gmail
On 03/20/2018 07:33 AM, Adam Thomson wrote:
This commit adds a power_supply class instance to represent a
PD source's voltage and current properties. This provides an
interface for reading these properties from user-space or other
drivers.
For PPS enabled Sources, this also provides write access
On 03/20/2018 07:33 AM, Adam Thomson wrote:
This commit adds the 'usb_type' property to represent USB supplies
which can report a number of different types based on a connection
event.
Examples of this already exist in drivers whereby the existing 'type'
property is updated, based on an event, t
On 03/20/2018 07:33 AM, Adam Thomson wrote:
This commit adds code to handle requesting of PPS APDOs. Switching
between standard PDOs and APDOs, and re-requesting an APDO to
modify operating voltage/current will be triggered by an
external call into TCPM.
Signed-off-by: Adam Thomson
Acked-by: He
On 03/20/2018 07:33 AM, Adam Thomson wrote:
This commit adds sink side support for Get_Status, Status,
Get_PPS_Status and PPS_Status handling. As there's the
potential for a partner to respond with Not_Supported,
handling of this message is also added. Sending of
Not_Supported is added to handle
A watchdog timer exception also occurs if the selected time base bit
transitions from 0 to 1 due
to an mtspr that writes a 1 to the bit when its previous value was 0.
Signed-off-by: Xiaofeng Wei
---
drivers/watchdog/booke_wdt.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/w
The current kexec_file ignores kexec_buf.top_down value when call
arch_kexec_walk_mem() to allocate memory for loading kernel/initrd
stuffs. This is not supposed to be what kexec_buf.top_down is used
for.
In patch 0001, introduce a new function walk_system_ram_res_rev()
which is a variant of walk_
From: AKASHI Takahiro
This function, being a variant of walk_system_ram_res() introduced in
commit 8c86e70acead ("resource: provide new functions to walk through
resources"), walks through a list of all the resources of System RAM
in reversed order, i.e., from higher to lower.
It will be used in
For kexec_file loading, if kexec_buf.top_down is 'true', the memory which
is used to load kernel/initrd/purgatory is supposed to be allocated from
top to down. This is also consistent with the old kexec loading interface.
However, the current arch_kexec_walk_mem() doesn't do like this. It ignores
When we dump the backtrace of some specific task, there is a potential race
condition due to the task may be running on other cores if SMP enabled.
That is because for current implementation, if the task is not the current
task, we will get the registers used for unwind from cpu_context saved in
th
On 21-03-18, 18:21, Shunyong Yang wrote:
> When multiple cpus are related in one cpufreq policy, the first online cpu
> will be chosen by default to handle cpufreq operations. In a CPPC case,
> let's take two related cpus, cpu0 and cpu1 as an example.
>
> After system start, cpu0 is the first onli
On Thu, Mar 22, 2018 at 09:52:18AM +0800, Jason Wang wrote:
>
>
> On 2018年03月20日 12:26, Jonathan Helman wrote:
> > > On Mar 19, 2018, at 7:31 PM, Jason Wang wrote:
> > >
> > >
> > >
> > > On 2018年03月20日 06:14, Jonathan Helman wrote:
> > > > Export the number of successful and failed hugetlb p
When we dump the backtrace of some specific task, there is a potential race
condition due to the task may be running on other cores if SMP enabled.
That is because for current implementation, if the task is not the current
task, we will get the registers used for unwind from cpu_context saved in
th
For generic pins, parameter "arg" is 0 or 1.
For special pins, bias-disable is set by R0R1,
so we need transmited "00" to set bias-disable
When we set "bias-disable" as high-z property,
the parameter should be "MTK_PUPD_SET_R1R0_00".
Signed-off-by: Zhiyong Tao
---
drivers/pinctrl/mediatek/pinctr
The commit includes mt2712 pinctrl driver.
Signed-off-by: Zhiyong Tao
---
drivers/pinctrl/mediatek/Kconfig |7 +
drivers/pinctrl/mediatek/Makefile |1 +
drivers/pinctrl/mediatek/pinctrl-mt2712.c | 634 +
drivers/pinctrl/mediatek/pinctrl-mtk-mt2712.h
This series includes five patches:
1.Add mt2712 pintcrl head file.
2.Add mt2712 pinctrl device node.
3.Add mt2712 pinctrl driver.
4.Support bias-disable of generic and special pins simultaneously.
5.fix check warnings.
Changes in patch v4:
1)fix check warnings for mt2712.
2)add fix check warnings
This patch adds pintcrl device node for mt2712.
Signed-off-by: Zhiyong Tao
---
arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 18 ++
1 file changed, 18 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt2712e.dtsi
b/arch/arm64/boot/dts/mediatek/mt2712e.dtsi
index d7688bc..f
This patch adds pinctrl file for mt2712.
Signed-off-by: Zhiyong Tao
Reviewed-by: Rob Herring
---
arch/arm64/boot/dts/mediatek/mt2712-pinfunc.h | 1123 +
1 file changed, 1123 insertions(+)
create mode 100644 arch/arm64/boot/dts/mediatek/mt2712-pinfunc.h
diff --git a/arc
On Wed, Mar 21, 2018 at 06:29:41PM -0700, Nick Terrell wrote:
> This patch set adds support for a ZSTD-compressed kernel and ramdisk
> images in the kernel boot process. It only integrates the support with
> x86, though the first patch is generic to all architectures.
I'm running this patch set si
On (03/21/18 19:56), Nick Terrell wrote:
[..]
> This seems like a reasonable extension to the algorithm, and it looks like
> LZ4_DYN is about a 5% improvement to compression ratio on your benchmark.
> The biggest question I have is if it is worthwhile to maintain a separate
> incompatible variant o
On 3/21/2018 11:15 PM, Colin King wrote:
From: Colin Ian King
The error return code is not being assigned to ret from the call
to clk_prepare_enable and consequently the current check on ret
picks up the previous error return. Fix this by adding in the
missing assignment to ret.
Detected by
On (03/22/18 11:14), Sergey Senozhatsky wrote:
[..]
> Looking at
>
> printk()->call_console_drivers()->serial8250_console_putchar()->wait_for_xmitr()
>
> ... wait_for_xmitr() can spin for over 1 second waiting for the UART_MSR_CTS
> bit.
[..]
> a 1+ second long busy loop in the console driver
Thanks very much for you hint!
On 03/21/2018 05:57 PM, Thomas Gleixner wrote:
> On Wed, 21 Mar 2018, Cao jin wrote:
>> On 03/17/2018 06:01 PM, Cao jin wrote:
>>> I find two small questions which confuse me a little.
>>>
>>> 1.
>>> # Check signature at end of setup
>>>cmpl$0x5a5aaa55,
On 2018/3/22 10:08, Yunlong Song wrote:
> Since f2fs_inode_info is allocated with flag GFP_F2FS_ZERO, so we do not
> need to initialize zero value for its member any more.
>
> Signed-off-by: Yunlong Song
Reviewed-by: Chao Yu
Thanks,
On Tue, Mar 6, 2018 at 9:56 PM, Maxime Ripard wrote:
> From: Maxime Ripard
>
> The A33 has a MIPI-DSI block, along with its D-PHY. Let's add it in order
> to use it in the relevant boards.
>
> Signed-off-by: Maxime Ripard
> ---
> arch/arm/boot/dts/sun8i-a33.dtsi | 44 +++
Hi Pavel,
On 21 March 2018 at 22:04, Pavel Machek wrote:
> On Wed 2018-03-21 19:30:16, Baolin Wang wrote:
>> We can register one notifier through register_reboot_notifier() function to
>> prepare to power off the system, then we can remove the
>> 'pm_power_off_prepare'
>> hook in following patch
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in:
drivers/gpu/drm/i915/gvt/scheduler.c
between commit:
fa3dd623e559 ("drm/i915/gvt: keep oa config in shadow ctx")
from Linus' tree and commit:
b20c0d5ce104 ("drm/i915/gvt: Update PDPs after a vGPU mm object is pinn
usbipd includes exported devices in response to exportable device list.
Exclude exported devices from exportable device list to avoid:
- import requests for devices that are exported only to fail the request.
- revealing devices that are imported by a client to another client.
Signed-off-by: Shua
On Tue, Mar 6, 2018 at 9:56 PM, Maxime Ripard wrote:
> From: Maxime Ripard
>
> Most of the Allwinner SoCs since the A31 share the same MIPI-DSI
> controller.
>
> While that controller is mostly undocumented, the code is out there and has
> been cleaned up in order to be integrated into DRM. Howev
Hi, Dmitry and Lee
The series seems not being got merged. Are they good enough to be ready
into the your tree?
Recently I've tested the series with focusing on pwrkey event generated
through interrupt when push and release the key on bpi-r2 board and then
finally it's working fine. but for homeke
Hello Steven,
On (03/21/18 09:44), Steven Rostedt wrote:
[..]
> > #4 [881ffb0b7540] delay_tsc at 81326724
> > #5 [881ffb0b7548] __const_udelay at 81326678
> > #6 [881ffb0b7558] wait_for_xmitr at 814056e0
> > #7 [881ffb0b7580] serial8250_console_putchar a
Hi Martin,
Commit
339faa8150fd ("scsi: smartpqi: workaround fw bug for oq deletion")
is missing a Signed-off-by from its author.
--
Cheers,
Stephen Rothwell
pgpAo2j4xF3lb.pgp
Description: OpenPGP digital signature
The patch
regulator: qcom_smd: Drop regulator/{machine,of_regulator} includes
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in
It's too easy to build the initrd with wrong options during testing, after
which it may silently work anyway.
Signed-off-by: Adam Borowski
---
lib/decompress.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/lib/decompress.c b/lib/decompress.c
index ab3fc90ffc64..556b9d916
Since f2fs_inode_info is allocated with flag GFP_F2FS_ZERO, so we do not
need to initialize zero value for its member any more.
Signed-off-by: Yunlong Song
---
fs/f2fs/super.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
index 0c1fe9b..42d564c 100644
In case of error, the function devm_ioremap_resource() returns ERR_PTR()
and never returns NULL. The NULL test in the return value check should
be replaced with IS_ERR().
Fixes: f079b6406348 ("staging: mt7621-eth: add gigabit switch driver (GSW)")
Signed-off-by: Wei Yongjun
---
drivers/staging/m
In case of error, the function devm_ioremap_resource() returns ERR_PTR()
and never returns NULL. The NULL test in the return value check should
be replaced with IS_ERR().
Fixes: e3cbf478f846 ("staging: mt7621-eth: add the drivers core files")
Signed-off-by: Wei Yongjun
---
drivers/staging/mt7621
In case of error, the function of_phy_connect() returns NULL pointer not
ERR_PTR(). The IS_ERR() test in the return value check should be
replaced with NULL test.
Fixes: e3cbf478f846 ("staging: mt7621-eth: add the drivers core files")
Signed-off-by: Wei Yongjun
---
drivers/staging/mt7621-eth/mdi
Fixes the following sparse warning:
drivers/staging/mt7621-gpio/gpio-mt7621.c:47:3: warning:
symbol 'gc_map' was not declared. Should it be static?
Signed-off-by: Wei Yongjun
---
drivers/staging/mt7621-gpio/gpio-mt7621.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drive
Found a patch which solves the dependency issue. In my testing (on
4.9, with Windows 2016, and also to Samba) as Pavel suggested this
appears to fix the problem, but I will let Srivatsa confirm that it
also fixes it for him. The two attached patches for 4.9 should work.
As an aside which may hel
On Wed, Mar 21, 2018 at 08:32:54PM -0400, Jerome Glisse wrote:
> > I am testing with drivers/char/hmm_dmirror.c from your git repository.
> >
> > The addr I got (before "- size") is actually 0x7f, so equally
> > (1 << 40).
> >
> > So from your reply, it seems to me that HMM is supposed t
Error injection is a useful mechanism to fail arbitrary kernel
functions. However, it is often hard to guarantee an error propagates
appropriately to user space programs. By injecting into syscalls, we can
return arbitrary values to user space directly; this increases
flexibility and robustness in
The definition of the GICR_CTLR.RWP control bit was expanded to indicate
status of changing GICR_CTLR.EnableLPI from 1 to 0 is being in progress
or completed. Software must observe GICR_CTLR.RWP==0 after clearing
GICR_CTLR.EnableLPI from 1 to 0 and before writing GICR_PENDBASER and/or
GICR_PROPBASE
On 2018年03月20日 12:26, Jonathan Helman wrote:
On Mar 19, 2018, at 7:31 PM, Jason Wang wrote:
On 2018年03月20日 06:14, Jonathan Helman wrote:
Export the number of successful and failed hugetlb page
allocations via the virtio balloon driver. These 2 counts
come directly from the vm_events HTLB_B
Hello,
Facebook is given out 14,000,000.USD (Fourteen Million Dollars) its all about
14 Please, respond with your Unique Code (FB/BF14-13M5250UD) using your
registration email, to the Verification Department at;
dustinmoskovitz.facebo...@gmail.com
Dustin Moskovitz
Facebook Team
Copyright © 2
Hi
On Tuesday, March 20, 2018 06:20 PM, Emil Velikov wrote:
On 20 March 2018 at 06:24, hl wrote:
Hi Emil,
On Monday, March 19, 2018 09:09 PM, Emil Velikov wrote:
On 15 March 2018 at 02:35, hl wrote:
Hi Emil,
On Wednesday, March 14, 2018 08:02 PM, Emil Velikov wrote:
Hi Lin,
On 14 M
Handling of restarting a system call for nosig should be done after
all possible calls of do_signal, to see if one of them actually
delivers signal or not.
Before this change, restarting a system call for nosig may be followed
by a call of handle_signal which would try to change the system call
re
do_signal may be called multiple times from exit_to_usermode_loop. In
those multiple calls, only the one should handle restarting the system
call.
When actually delivering a signal, make sure the register will not be
examined again as syscall errno by another call of do_signal.
Signed-off-by: NI
Call to restore_saved_sigmask is only needed when it is from a system
call. It is only woken up system call which uses saved_sigmask.
Specifically, they are pselect, ppoll, and epoll_pwait.
Signed-off-by: NIIBE Yutaka
---
arch/x86/kernel/signal.c | 12 ++--
1 file changed, 6 insertions(
Make a function for swing at the ball but actually no ball.
Signed-off-by: NIIBE Yutaka
---
arch/x86/include/asm/signal.h | 1 +
arch/x86/kernel/signal.c | 5 +
2 files changed, 6 insertions(+)
diff --git a/arch/x86/include/asm/signal.h b/arch/x86/include/asm/signal.h
index 5f9012ff52e
Hello,
Background:
I tried to fix my own problem in suspend-to-ram with USB devices (some
device doesn't work well after suspend/resume). I know it's common
problems. Well, while I identified some problems of USB devices and
drivers, I did try my best. I fixed a USB device implementation of
min
On Wed, Mar 21, 2018 at 3:11 PM, Bae, Chang Seok
wrote:
> On 3/20/18, 17:47, "Andy Lutomirski" wrote:
>>If I've understood all your emails right, when you looked at existing
>>ptrace users, you found that all of them that write to gs and/or
>>gs_base do it as part of a putregs call th
On Wed, Mar 21, 2018 at 7:01 AM, Metzger, Markus T
wrote:
>> -Original Message-
>> From: Andy Lutomirski [mailto:l...@kernel.org]
>> Sent: 21 March 2018 01:47
>
> Hello Andy,
>
>> I retract this particular comment. But I still think that all this
>> complexity needs to
>> be more clearly
On Wed, Mar 21, 2018 at 11:15:16AM +0530, Mukunda,Vijendar wrote:
> There is a patch dependency .
> Below patch not merged yet. We submitted for upstream review.
> [PATCH V2] ASoC: dwc: I2S Controller instance param added
You need to mention dependencies between patches when publishing and I
don'
On Wed, Mar 21, 2018 at 10:03 PM, H. Peter Anvin wrote:
> On 03/20/18 07:58, Andy Lutomirski wrote:
>>> On Mar 19, 2018, at 10:49 AM, Chang S. Bae wrote:
>>>
>>> When FSGSBASE is enabled, SWAPGS needs if and only if (current)
>>> GS base is not the kernel's.
>>>
>>> FSGSBASE instructions allow us
On Wed, Mar 21 2018, James Hogan wrote:
> On Tue, Mar 20, 2018 at 07:29:51PM +1100, NeilBrown wrote:
>>
>> ralink_halt() does nothing that machine_halt()
>> doesn't already do, so it adds no value.
>>
>> It actually causes incorrect behaviour due to the
>> "unreachable()" at the end. This tell
On Wed, Mar 21, 2018 at 05:11:10PM -0700, John Hubbard wrote:
> On 03/21/2018 04:37 PM, Jerome Glisse wrote:
> > On Wed, Mar 21, 2018 at 04:10:32PM -0700, John Hubbard wrote:
> >> On 03/21/2018 03:46 PM, Jerome Glisse wrote:
> >>> On Wed, Mar 21, 2018 at 03:16:04PM -0700, John Hubbard wrote:
>
On 3/22/2018 2:52 AM, Arnaldo Carvalho de Melo wrote:
Em Wed, Mar 21, 2018 at 05:04:46PM +0100, Jiri Olsa escreveu:
On Wed, Mar 21, 2018 at 12:43:15PM -0300, Arnaldo Carvalho de Melo wrote:
Em Wed, Mar 21, 2018 at 12:40:35PM -0300, Arnaldo Carvalho de Melo escreveu:
Em Wed, Mar 21, 2018 at 0
From: Jérôme Glisse
This code was lost in translation at one point. This properly call
mmu_notifier_unregister_no_release() once last user is gone. This
fix the zombie mm_struct as without this patch we do not drop the
refcount we have on it.
Changed since v1:
- close race window between a las
On Wed, Mar 21, 2018 at 01:44:25PM -0400, Daniel Jordan wrote:
> On 03/20/2018 04:54 AM, Aaron Lu wrote:
> ...snip...
> > reduced zone->lock contention on free path from 35% to 1.1%. Also, it
> > shows good result on parallel free(*) workload by reducing zone->lock
> > contention from 90% to almost
From: Ralph Campbell
The hmm_mirror_register() function registers a callback for when
the CPU pagetable is modified. Normally, the device driver will
call hmm_mirror_unregister() when the process using the device is
finished. However, if the process exits uncleanly, the struct_mm
can be destroyed
On Tue, Mar 20, 2018 at 7:42 AM, Alexander Duyck
wrote:
>
> Instead of framing this as an enhanced version of the read/write ops
> why not look at replacing or extending something like the
> memcpy_fromio or memcpy_toio operations?
Yes, doing something like "memcpy_fromio_avx()" is much more
pala
On 23-02-18, 15:53, Viresh Kumar wrote:
> Problem statement:
>
> Some devices are powered ON by the bootloader before the bootloader
> handovers control to Linux. It maybe important for some of those devices
> to keep working until the time a Linux device driver probes the device
> and reconfigure
Adrian,
> Here is V3, now re-based on top of patch "scsi: ufs: sysfs:reworking of the
> rpm_lvl and spm_lvl entries".
>
> Michał Potomski has previously sent a patch for Auto-Hibernate, but this
> patch is slightly different, based on the latest ufs-sysfs changes, it also
> takes care to restore
Adrian,
> On 01/03/18 12:48, Stanislav Nijnikov wrote:
>> Read from these files will return the integed value of the chosen power
>> management level now. Separate entries were added to show the target
>> UFS device and UIC link states. The description of the possible power
>> managements levels
Hi, Laurent
2018-03-14 1:59 GMT+08:00 Laurent Dufour :
> This is a port on kernel 4.16 of the work done by Peter Zijlstra to
> handle page fault without holding the mm semaphore [1].
>
> The idea is to try to handle user space page faults without holding the
> mmap_sem. This should allow better co
On 03/21/2018 10:58 AM, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
Add support for Xen para-virtualized frontend display driver.
Accompanying backend [1] is implemented as a user-space application
and its helper library [2], capable of running as a Weston client
or DRM maste
1 - 100 of 926 matches
Mail list logo
