Hi Greg,
Today's linux-next merge of the staging tree got conflicts in:
drivers/staging/ccree/Kconfig
drivers/staging/ccree/Makefile
between commit:
e294ca1cca3a ("staging: ccree: rename staging ver and mark as broken")
from the crypto tree and commit:
8b0217965418 ("staging: ccree: r
Am 14.03.2018 um 20:07 schrieb Jakob Unterwurzacher:
On 14.03.18 11:04, Wolfgang Grandegger wrote:
(000.000443) can0 2034 [8] 00 0C 00 00 00 00 78 00
ERRORFRAME
controller-problem{rx-error-warning,tx-error-warning}
transceiver-status
no-acknowledgement-on-tx
error-
On Wed, Mar 14, 2018 at 9:25 PM, Michael S. Tsirkin wrote:
> On Wed, Mar 14, 2018 at 07:25:36PM +0100, Greg KH wrote:
>> On Tue, Mar 13, 2018 at 07:40:51PM +0200, Michael S. Tsirkin wrote:
>> > I think it's a good idea to use sysfs for this. However,
>> > there are a couple of missing interfaces h
On 3/12/2018 6:44 PM, Abhishek Sahu wrote:
> The role of FLUSH and EOT tag is to flush already scheduled
> descriptors in BAM HW in case of error. EOT is required only
> when descriptors are scheduled in RX FIFO. If all the messages
> are WRITE, then only FLUSH tag will be used.
>
> A single BAM
Hello everyone,
I got a warning as below which is a AB-BA deadlock issue. But I don't understand
how the 'existing dependency' happened.
It looks like: kvm_read_guest() held (&mm->mmap_sem), then reading userspace
memory
(which is not ready yet) caused page_fault() invoked, then in i915_gem_faul
Hi Greg,
After merging the tty tree, today's linux-next build (arm
multi_v7_defconfig) produced these warnings:
drivers/tty/serial/stm32-usart.c:155:12: warning: 'stm32_init_rs485' defined
but not used [-Wunused-function]
static int stm32_init_rs485(struct uart_port *port,
^
According to AM335x TRM[1] 14.3.6.2, AM437x TRM[2] 15.3.6.2 and
DRA7 TRM[3] 24.11.4.8.7.3.3, in-band mode in EXT_EN(bit18) register is only
available when PHY is configured in RGMII mode with 10Mbps speed. It will
cause some networking issues without RGMII mode, such as carrier sense
errors and low
On Thursday 15 March 2018 12:55 AM, Richard Weinberger wrote:
Am Mittwoch, 14. März 2018, 19:56:52 CET schrieb Boris Brezillon:
On Fri, 9 Mar 2018 16:20:49 +0530
Arvind Yadav wrote:
if device_register() returned an error! Always use put_device()
to give up the reference initialized.
Signe
From: Ching Huang
Change driver version to v1.40.00.05-20180309
Signed-off-by: Ching Huang
---
diff --git a/drivers/scsi/arcmsr/arcmsr.h b/drivers/scsi/arcmsr/arcmsr.h
index 842b77a..2e51ccc 100755
--- a/drivers/scsi/arcmsr/arcmsr.h
+++ b/drivers/scsi/arcmsr/arcmsr.h
@@ -49,7 +49,7 @@ struct d
On 15 March 2018 at 02:32, Daniel Vacek wrote:
> On Wed, Mar 14, 2018 at 6:36 PM, Ard Biesheuvel
> wrote:
>> On 14 March 2018 at 16:41, Ard Biesheuvel wrote:
>>> On 14 March 2018 at 15:54, Ard Biesheuvel wrote:
On 14 March 2018 at 14:54, Michal Hocko wrote:
> On Wed 14-03-18 14:35:12,
From: Ching Huang
Sleep to avoid CPU stuck too long for waiting adapter ready.
Signed-off-by: Ching Huang
---
diff --git a/drivers/scsi/arcmsr/arcmsr_hba.c b/drivers/scsi/arcmsr/arcmsr_hba.c
index 2f52c53..732b5d9 100755
--- a/drivers/scsi/arcmsr/arcmsr_hba.c
+++ b/drivers/scsi/arcmsr/arcmsr_h
2018-03-15 3:32 GMT+09:00 Nicolas Pitre :
> On Thu, 15 Mar 2018, Masahiro Yamada wrote:
>
>> If CONFIG_TRIM_UNUSED_KYMS is enabled, KBUILD_MODULES is set.
>
> Not when you do "make vmlinux" though.
I could not understand this.
Unless I am missing something,
I think this code is always parsed.
Hi Greg,
Today's linux-next merge of the tty tree got conflicts in:
drivers/tty/hvc/Kconfig
drivers/tty/hvc/Makefile
between commit:
c235c62f99e6 ("tty: remove bfin_jtag_comm and hvc_bfin_jtag drivers")
from the asm-generic tree and commit:
afa6b1ccfad5 ("tty: New RISC-V SBI console d
Do you need a loan
From: Ching Huang
Handle adapter removed due to thunderbolt cable disconnection.
Signed-off-by: Ching Huang
---
diff --git a/drivers/scsi/arcmsr/arcmsr_hba.c b/drivers/scsi/arcmsr/arcmsr_hba.c
index 75e828b..2f52c53 100755
--- a/drivers/scsi/arcmsr/arcmsr_hba.c
+++ b/drivers/scsi/arcmsr/arcmsr
Hi,
On Thursday 15 March 2018 11:47 AM, Chen-Yu Tsai wrote:
> Hi Kishon,
>
> On Fri, Feb 16, 2018 at 7:20 PM, Kishon Vijay Abraham I wrote:
>>
>>
>> On Friday 19 January 2018 08:15 PM, Maxime Ripard wrote:
>>> On Fri, Jan 19, 2018 at 05:25:41PM +0800, Chen-Yu Tsai wrote:
The AXP223 PMIC, li
Hi Greg,
Today's linux-next merge of the tty tree got conflicts in:
arch/arm/boot/dts/stih407-b2120.dts
arch/arm/boot/dts/stih410-b2120.dts
arch/arm/boot/dts/stih410-b2260.dts
arch/arm/boot/dts/stih418-b2199.dts
between commit:
db5430663017 ("arm: dts: replace 'linux,stdout-path' with
2018-03-15 2:26 GMT+09:00 Nicolas Pitre :
> On Thu, 15 Mar 2018, Masahiro Yamada wrote:
>
>> From the comment, I expect this code creates autoksyms.h in case it
>> is missing, but it actually touches it when it does exists.
>
> Oops, indeed.
>
>> Signed-off-by: Masahiro Yamada
>> ---
>>
>> I do no
From: Ching Huang
Rename ACB_F_BUS_HANG_ON to ACB_F_ADAPTER_REMOVED for adapter hot-plug.
Signed-off-by: Ching Huang
---
diff --git a/drivers/scsi/arcmsr/arcmsr.h b/drivers/scsi/arcmsr/arcmsr.h
index f375f35..842b77a 100755
--- a/drivers/scsi/arcmsr/arcmsr.h
+++ b/drivers/scsi/arcmsr/arcmsr.h
nconf.h includes and "ncurses.h", but it does not need to
include both. Generally, it should fall back to curses.h only when
ncurses.h is not found. But, looks like it has never happened;
these includes have been here for many years since commit 692d97c380c6
("kconfig: new configuration interfac
From: Ching Huang
This patch series are against to mkp's 4.17/scsi-queue.
1. Rename ACB_F_BUS_HANG_ON to ACB_F_ADAPTER_REMOVED for adapter hot-plug
2. Handle adapter removed due to thunderbolt cable disconnection.
3. Sleep to avoid CPU stuck too long for waiting adapter ready
4. Change driver ve
On Thu, Mar 15, 2018 at 2:50 AM, Robin Murphy wrote:
> On 13/03/18 08:55, Vivek Gautam wrote:
>>
>> From: Sricharan R
>>
>> Finally add the device link between the master device and
>> smmu, so that the smmu gets runtime enabled/disabled only when the
>> master needs it. This is done from add_dev
The FastReg support in ko2iblnd was not unmapping pool items
causing the items to leak. In addition, the mapping code
is not growing the pool like we do with FMR.
This patch makes sure we are unmapping FastReg pool elements
when we are done with them. It also makes sure the pool
will grow when w
Hi Kishon,
On Fri, Feb 16, 2018 at 7:20 PM, Kishon Vijay Abraham I wrote:
>
>
> On Friday 19 January 2018 08:15 PM, Maxime Ripard wrote:
>> On Fri, Jan 19, 2018 at 05:25:41PM +0800, Chen-Yu Tsai wrote:
>>> The AXP223 PMIC, like the AXP221, does not generate VBUS change
>>> interrupts when N_VBUSE
On Wed, Mar 14, 2018 at 07:19:25AM -0700, James Bottomley wrote:
> On Wed, 2018-03-14 at 14:08 +0800, joeyli wrote:
> > On Tue, Mar 13, 2018 at 10:18:35AM -0700, James Bottomley wrote:
> > >
> > > On Tue, 2018-03-13 at 18:38 +0800, Lee, Chun-Yi wrote:
> > > >
> > > > This patch adds the logic for
On Wed, Mar 14, 2018 at 10:06 PM, Darrick J. Wong
wrote:
> On Sat, Mar 10, 2018 at 10:17:45AM -0800, Andiry Xu wrote:
>> From: Andiry Xu
>>
>> inode.h defines the non-volatile and volatile NOVA inode data structures.
>>
>> The non-volatile NOVA inode (nova_inode) is aligned to 128 bytes and conta
Hi Jonathan,
I have been looking at the IIO ABI docs and if I understand correctly, the idea
is to use consistent naming conventions? So for example, looking at the ADE7854
datasheet, the naming matching the ADE7854 registers would be as follows:
{direction}_{type}_{index}_{modifier}_{info_mask
On Wed, Mar 14, 2018 at 9:54 PM, Darrick J. Wong
wrote:
> On Sat, Mar 10, 2018 at 10:17:44AM -0800, Andiry Xu wrote:
>> From: Andiry Xu
>>
>> This header file defines NOVA persistent and volatile superblock
>> data structures.
>>
>> It also defines NOVA block layout:
>>
>> Page 0: Superblock
>> P
On Wed, Mar 14, 2018 at 5:33 PM, Randy Dunlap wrote:
> On 03/10/2018 10:19 AM, Andiry Xu wrote:
>> Sysfs support allows user to get/post information of running NOVA instance.
>> After mount, NOVA creates four entries under proc directory
>> /proc/fs/nova/pmem#/:
>>
>> timing_stats IO_stats
It's been missing for a while but no one is touching that up. Fix it.
CC: Steven Rostedt
CC: Ingo Molnar
Signed-off-by: Peter Xu
---
kernel/trace/trace_entries.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/trace/trace_entries.h b/kernel/trace/trace_entries.h
ind
On 03/13/18 22:23, Andy Shevchenko wrote:
> On Tue, Mar 13, 2018 at 9:34 PM, Kirill Marinushkin
> wrote:
>> In the current implementation, `rmmod snd_bcm2835` does not release
>> resources properly. It causes an oops when trying to list sound devices.
>>
>> This commit fixes it.
> Nice catch!
>
>
2018-03-13 11:30 GMT+09:00 Randy Dunlap :
> From: Randy Dunlap
>
> Each of 'make {menu,n,g,x}config' uses (needs) pkg-config to make sure
> that other required files are present, but none of these check that
> pkg-config itself is present. Add a check for all 4 of these targets.
>
> Fixes kernel
Hi Masami,
On 03/08/2018 02:20 PM, Masami Hiramatsu wrote:
> Add array type support for probe events.
> This allows user to get arraied types from memory address.
> The array type syntax is
>
> TYPE[N]
>
> Where TYPE is one of types (u8/16/32/64,s8/16/32/64,
> x8/16/32/64, symbol, string) an
On Tue, Mar 13, 2018 at 3:20 AM, Peter Zijlstra wrote:
> On Sun, Mar 11, 2018 at 10:15:55AM -0700, Dan Williams wrote:
>> On Sun, Mar 11, 2018 at 4:27 AM, Peter Zijlstra wrote:
>> > On Fri, Mar 09, 2018 at 10:55:32PM -0800, Dan Williams wrote:
>> >> Add a generic facility for awaiting an atomic_t
Hi Arnd,
On Wed, 14 Mar 2018 16:35:13 +0100
Arnd Bergmann wrote:
> Hi driver maintainers,
>
> I just posted one series with the removal of eight architectures,
> see https://lkml.org/lkml/2018/3/14/505 for details, or
> https://lwn.net/Articles/748074/ for more background.
>
> These are the de
Hi Marc,
Today's linux-next merge of the irqchip tree got a conflict in:
drivers/irqchip/Makefile
between commit:
abe45fd9f1b0 ("irqchip: Andestech Internal Vector Interrupt Controller
driver")
from the nds32 tree and commit:
f55c73aef890 ("irqchip/pdc: Add PDC interrupt controller for
On Wed, Mar 14, 2018 at 09:40:28PM +0100, Arnd Bergmann wrote:
> On Wed, Mar 14, 2018 at 9:31 PM, Dominik Brodowski
> wrote:
> > On Wed, Mar 14, 2018 at 03:43:47PM +0100, Arnd Bergmann wrote:
> >> The frv, tile and blackfin architectures are being removed, so
> >> we can clean up this header by re
On Tue, Mar 13, 2018 at 04:46:38PM +, Craig Tatlor wrote:
> The compatible string was mistakenly pulled from the downstream tree and the
> startup delay property is needed to prevent io errors on initial page select.
>
> Signed-off-by: Craig Tatlor
Thanks for the patch. I'll add Bjorn's rev
On Sat, Mar 10, 2018 at 10:17:45AM -0800, Andiry Xu wrote:
> From: Andiry Xu
>
> inode.h defines the non-volatile and volatile NOVA inode data structures.
>
> The non-volatile NOVA inode (nova_inode) is aligned to 128 bytes and contains
> file/directory metadata information. The most important f
Hi Mark,
Today's linux-next merge of the spi tree got a conflict in:
drivers/spi/Kconfig
between commit:
588020dcb92a ("treewide: simplify Kconfig dependencies for removed archs")
from the asm-generic tree and commit:
e3d001a0c29d ("spi: kconfig: Remove AVR32 dep. from SPI_ATMEL")
from
On Sat, Mar 10, 2018 at 10:17:44AM -0800, Andiry Xu wrote:
> From: Andiry Xu
>
> This header file defines NOVA persistent and volatile superblock
> data structures.
>
> It also defines NOVA block layout:
>
> Page 0: Superblock
> Page 1: Reserved inodes
> Page 2 - 15: Reserved
> Page 16 - 31: In
On Wed, 14 Mar 2018, Nicolas Pitre wrote:
> On Wed, 14 Mar 2018, Arnd Bergmann wrote:
>
> > The m32r architecture is getting removed, so this part can be
> > cleaned up as well.
> >
> > Signed-off-by: Arnd Bergmann
>
> Acked-by: Nicolas Pitre
>
> > ---
> > drivers/net/ethernet/smsc/Kconfig
Stephen,
> In preparation to enabling -Wvla, remove VLAs and replace them with
> fixed-length arrays instead.
>
> The arrays fixed here, using the number of constant sections, aren't
> really VLAs, but they appear so to the compiler. Replace the array
> sizes with a pre-processor-level constant i
Hi,
I have a ASUS AIO V222GA and another Acer Desktop XC-830 both
have Intel CPU J5005 and they both hit the same problem. The XHCI
connected USB keyboard/mouse can never wakeup the system from suspend.
It reminds me that similiar thing happens on ApolloLake too which
needs the XHCI_PME_STUCK_
Stephen,
> bfad_bsg.c uses a variable-length array declaration to measure the
> size of a putative array; this can be replaced by the product of the
> size of an element and the number of elements, avoiding the VLA
> altogether.
>
> - sizeof(wwn_t[iocmd->nports])) != BFA_STATUS_OK) {
On Wed, Mar 14, 2018 at 12:34 PM, Stephen Bates wrote:
>> P2P over PCI/PCI-X is quite common in devices like raid controllers.
>
> Hi Dan
>
> Do you mean between PCIe devices below the RAID controller? Isn't it pretty
> novel to be able to support PCIe EPs below a RAID controller (as opposed to
On Wed, Mar 14, 2018 at 05:32:13PM -0500, Eddie James wrote:
> From: Christopher Bostic
>
> Add a struct gpio_chip and define some methods so that this device's
> I/O can be accessed via /sys/class/gpio.
>
> Signed-off-by: Christopher Bostic
> Signed-off-by: Andrew Jeffery
> Signed-off-by: Edd
On Wed, Mar 14, 2018 at 05:32:14PM -0500, Eddie James wrote:
> From: Christopher Bostic
>
> Expose the gpiN_fault fields of mfr_status as individual debugfs
> attributes. This provides a way for users to be easily notified of gpi
> faults. Also provide the whole mfr_status register in debugfs.
>
bumping for review
On Sat, Mar 3, 2018 at 10:50 PM, Nick Desaulniers
wrote:
> Fixes commit 2be04df5668d ("certs/blacklist_nohashes.c: fix const confusion
> in certs blacklist")
>
> Signed-off-by: Nick Desaulniers
> ---
> certs/blacklist.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> iscsi tcp will first send out data, then calculate and send data
> digest. If we don't have BDI_CAP_STABLE_WRITES, the page cache will
> be written in spite of the on going writeback. Consequently, wrong
> digest will be got and sent to target.
>
> To fix this, set BDI_CAP_STABLE_WRITES when dat
> Never directly free @dev after calling device_register(), even
> if it returned an error! Always use put_device() to give up the
> reference initialized.
Lee, Chris: Please review!
--
Martin K. Petersen Oracle Linux Engineering
Hi Wolfgang,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0aa3fdb8b3a6df3c2e3b61dbfe079db9d30e03cd
commit: 6cdeaed3b1420bd2569891be0c4123ff59628e9e media: dvb_usb_pctv452e:
module refcount changes were unbalanced
On Thu, 15 Mar 2018, Borislav Petkov wrote:
> On Wed, Mar 14, 2018 at 10:00:14PM -0300, Henrique de Moraes Holschuh wrote:
> > Intel takes anything from twenty thousand cycles to several *million*
> > cycles per core, proportional to microcode update size.
>
> Got any hard data to back that claim
Stephen,
>> It would be useful if those configurations were not left behind so
>> that Linux could feasibly deploy offload code to a controller in the
>> PCI domain.
>
> Agreed. I think this would be great. Kind of like the XCOPY framework
> that was proposed a while back for SCSI devices [1]
Colin,
> There are several unions that are local to the source and do not need
> to be in global scope, so make them static. Also add in a missing void
> parameter to functions lpfc_nvme_cmd_template and
> lpfc_nvmet_cmd_template to clean up non-ANSI warning.
Applied to 4.17/scsi-queue. Thanks!
Hi all,
Today's linux-next merge of the drm-misc tree got a conflict in:
sound/pci/hda/hda_intel.c
between commits:
1ba8f9d30817 ("ALSA: hda: Add a power_save blacklist")
40088dc4e1ea ("ALSA: hda - Revert power_save option default value")
from Linus' tree and commit:
07f4f97d7b4b ("vg
On 3/14/2018 9:54 PM, Arnaldo Carvalho de Melo wrote:
Em Wed, Mar 14, 2018 at 10:04:49AM +0800, Jin, Yao escreveu:
On 3/13/2018 11:20 PM, Arnaldo Carvalho de Melo wrote:
Em Tue, Mar 13, 2018 at 10:16:50PM +0800, Jin Yao escreveu:
There is a requirement to let perf annotate support displayi
On Thu, Feb 08, 2018 at 02:47:10PM +0800, Shawn Guo wrote:
> On Mon, Jan 22, 2018 at 07:07:47AM -0800, Andrey Smirnov wrote:
> > Platform device core assumes the ownership of dev.platform_data as
> > well as that it is dynamically allocated and it will try to kfree it
> > as a part of platform_devi
xenbus_command_reply() did not actually copy the response string and
leaked stack content instead.
Fixes: 9a6161fe73bd ("xen: return xenstore command failures via response
instead of rc")
Signed-off-by: Simon Gaiser
---
PS: AFAICS this is not a security issue since /dev/xen/xenbus is
normally o
Rafael J told me in order for the ACPI-based physical CPU hotplug to work,
there have to be objects in the ACPI namespace corresponding to all of the
processors in question. If they are not present, there is no way to signal
insertion and eject the processors safely.
But, Kernel calculates the pos
On Wed, Mar 14, 2018 at 2:44 PM, dbasehore . wrote:
> On Wed, Mar 14, 2018 at 3:22 AM, Marc Zyngier wrote:
>> On 02/03/18 02:08, dbasehore . wrote:
>>> On Thu, Mar 1, 2018 at 4:29 AM, Marc Zyngier wrote:
Hi Mark,
On 01/03/18 11:41, Mark Rutland wrote:
> On Wed, Feb 28, 2018 at
Hi Andy,
At 03/15/2018 01:24 AM, Andy Shevchenko wrote:
On Wed, Mar 14, 2018 at 12:28 PM, Dou Liyang wrote:
+static void __init acpi_update_possible_map(void)
+{
+ unsigned int cpu, nr = 0;
+
+ if (nr_cpu_ids <= nr_unique_ids)
+ return;
+
+ for_each_possible
Genuine offer
How are you today and your family, I am a citizen of Sudan but
currently staying in Burkina Faso. My name is Miss Mariam Dim Deng,
25years old originated from Sudan.
My late father Dr. Dominic Dim Deng was the former Minister for SPLA
Affair and Special Adviser to President Salva Kii
Hi Herbert,
Today's linux-next merge of the crypto tree got a conflict in:
drivers/crypto/bfin_crc.c
between commit:
1d77094897bc ("crypto: remove blackfin CRC driver")
from the asm-generic tree and commits:
f1b298103e14 ("crypto: bfin_crc - Add empty hash export and import")
5471f2e2
On Wed, Mar 14, 2018 at 1:52 PM, Arnd Bergmann wrote:
> On Wed, Mar 14, 2018 at 4:50 AM, Deepa Dinamani
> wrote:
>> The file arch/arm64/kernel/process.c needs asm/compat.h also to be
>> included directly since this is included conditionally from
>> include/compat.h. This does seem to be typical
On Wed, 2018-03-14 at 12:57 -0700, Tejun Heo wrote:
> Hello,
>
> On Sat, Mar 10, 2018 at 04:47:28AM +0100, Mike Galbraith wrote:
> > Some form of cpu_exclusive (preferably exactly that, but something else
> > could replace it) is needed to define sets that must not overlap any
> > other set at cre
Hi Boris,
Today's linux-next merge of the nand tree got a conflict in:
drivers/mtd/nand/Kconfig
(mostly moved to drivers/mtd/nand/raw/Kconfig)
drivers/mtd/nand/Makefile
(mostly moved to drivers/mtd/nand/raw/Makefile)
drivers/mtd/nand/bf5xx_nand.c
(renamed to drivers/mtd/nand/raw/bf5xx
On 14-03-18, 16:35, Arnd Bergmann wrote:
> The blackfin architecture is getting removed, so this driver is
> now obsolete.
>
> Signed-off-by: Arnd Bergmann
> ---
> drivers/cpufreq/Makefile | 1 -
> drivers/cpufreq/blackfin-cpufreq.c | 217
> -
> 2
This adds the algorithm to maintain a system wide PASID name space
for the PASID allocation. Previously we maintained a per IOMMU unit
PASID name space which is not suitable for some use cases. For an
example, one application (associated with one PASID) might talk to
two physical devices simultaneo
On 14-03-18, 16:35, Arnd Bergmann wrote:
> The cris architecture is getting removed, including the artpec3
> and etraxfs SoCs, so these cpufreq drivers are now unused.
>
> Signed-off-by: Arnd Bergmann
> ---
> drivers/cpufreq/Makefile | 2 -
> drivers/cpufreq/cris-artpec3-cpufreq.c
This patch switches PASID management for SVM from SVM specific
idr to the global idr.
Cc: Ashok Raj
Cc: Jacob Pan
Cc: Kevin Tian
Cc: Liu Yi L
Signed-off-by: Lu Baolu
Reviewed-by: Kevin Tian
---
drivers/iommu/intel-svm.c | 20 +---
include/linux/intel-iommu.h | 1 -
2 fil
By guaranteeing that the argument of XS_TRANSACTION_END is valid we can
assume that the transaction has been closed when we get an XS_ERROR
response from xenstore (Note that we already verify that it's a valid
transaction id).
Signed-off-by: Simon Gaiser
---
drivers/xen/xenbus/xenbus_dev_fronten
As we move the PASID idr out of SVM code and make it serving
as a global PASID name space, the consumer can specify a ptr
to bind it with a PASID. We shouldn't assume that each PASID
will be bond with a ptr of struct intel_svm anymore.
This patch cleans up a idr_for_each_entry() usage in the SVM
c
Hi,
This patch series is trying to change the scope of PASID management
used in Intel IOMMU driver from per IOMMU to driver global. This is
required for some cases where current per-IOMMU PASID name space
doesn't work. For an example, one application (associated with one
PASID) might talk to two p
Users of the xenbus functions should never close a non existent
transaction (for example by trying to closing the same transaction
twice) but better catch it in xs_request_exit() than to corrupt the
reference counter.
Signed-off-by: Simon Gaiser
---
drivers/xen/xenbus/xenbus_xs.c | 4 +++-
1 fil
Commit fd8aa9095a95 ("xen: optimize xenbus driver for multiple
concurrent xenstore accesses") made a subtle change to the semantic of
xenbus_dev_request_and_reply() and xenbus_transaction_end().
Before on an error response to XS_TRANSACTION_END
xenbus_dev_request_and_reply() would not decrement th
Hi Emil,
On Wednesday, March 14, 2018 08:02 PM, Emil Velikov wrote:
Hi Lin,
On 14 March 2018 at 09:12, Lin Huang wrote:
From: huang lin
Refactor Innolux P079ZCA panel driver, let it support
multi panel.
Change-Id: If89be5e56dba8cb498e2d50c1bbeb0e8016123a2
Signed-off-by: Lin Huang
---
Cha
On 03/14/2018 06:48 PM, Daniel Kurtz wrote:
> Commit 470ca0de69fe ("serial: earlycon: Enable earlycon without command
> line param") added EARLYCON_TABLE().
>
> Commit 99492c39f39f ("earlycon: Fix __earlycon_table stride") referenced
> commit 07fca0e57fca92 ("tracing: Properly align linker defined
On Wed, Mar 14, 2018 at 6:36 PM, Ard Biesheuvel
wrote:
> On 14 March 2018 at 16:41, Ard Biesheuvel wrote:
>> On 14 March 2018 at 15:54, Ard Biesheuvel wrote:
>>> On 14 March 2018 at 14:54, Michal Hocko wrote:
On Wed 14-03-18 14:35:12, Ard Biesheuvel wrote:
> On 14 March 2018 at 14:13,
Linus,
> I've pulled it, but I don't see why (and how) this kind of garbage got
> reviewed and acked by multiple people.
My bad. I actually did notice the superfluous ifs and meant to nuke them
when I committed the patch.
However, I had a freak accident with my fixes branch that day that
compel
The use of stack Variable Length Arrays needs to be avoided, as they
can be a vector for stack exhaustion, which can be both a runtime bug
(kernel Oops) or a security flaw (overwriting memory beyond the
stack). Also, in general, as code evolves it is easy to lose track of
how big a VLA can get. Thu
On Wed, Mar 14, 2018 at 05:26:24PM -0500, Grygorii Strashko wrote:
> Some ethernet drivers (like TI CPSW) may connect and manage >1 Net PHYs per
> one netdevice, as result such drivers will produce warning during system
> boot and fail to connect second phy to netdevice when PHYLIB framework
> will
On Wed, Mar 14, 2018 at 8:29 PM, Ard Biesheuvel
wrote:
> This reverts commit 864b75f9d6b0100bb24fdd9a20d156e7cda9b5ae.
>
> Commit 864b75f9d6b0 ("mm/page_alloc: fix memmap_init_zone pageblock
> alignment") modified the logic in memmap_init_zone() to initialize
> struct pages associated with invalid
On Mon, Mar 12, 2018 at 10:29:07PM -0600, Tycho Andersen wrote:
> Similarly to the previous patch, we would like to get rid of stack
> allocated arrays: https://lkml.org/lkml/2018/3/7/621
>
> In this case, we can also use a malloc style approach to free the temporary
> buffer, being careful to als
On 3/14/2018 9:44 PM, Alexander Duyck wrote:
> On Wed, Mar 14, 2018 at 3:57 PM, Sinan Kaya wrote:
>> Hi Alexander,
>>
>> On 3/14/2018 5:49 PM, Alexander Duyck wrote:
>>> On Wed, Mar 14, 2018 at 5:13 AM, wrote:
On 2018-03-14 01:08, Timur Tabi wrote:
>
> On 3/13/18 10:20 PM, Sinan Kay
AMD Carrizo / Stoneyridge use a DesignWare 8250 UART that uses a 48 MHz
input clock. Currently, there is no way to tell earlycon to use a specific
uart input clock when configuring a baud rate.
Patch 1 adds an earlycon ->setup() callback to set up this clock. The setup is
triggered on the comman
AMD Carrizo / Stoneyridge use a DesignWare 8250 UART that uses a special
earlycon setup handler to configure its input clock in order to compute
baud rate divisor registers.
Detect them by examining the OEMID field in the SPCR header, and pass
then pass uart type amdcz to earlycon.
Signed-off-by:
The old_serial_port global array in 8250_core is supposed to hold an entry
for each serial port on the system that cannot be discovered via a
standard enumeration mechanism (aka ACPI/PCI/DTS). The array is populated
at compile-time from the value specified in the SERIAL_PORT_DFNS macro.
This macro
AMD Carrizo / Stoneyridge use a DesignWare 8250 UART that uses a 48 MHz
input clock. Currently, there is no way to tell earlycon to use a specific
uart input clock when configuring a baud rate.
Patch 1 adds an earlycon ->setup() callback to set up this clock. The setup is
triggered on the comman
AMD Carrizo / Stoneyridge use a DesignWare 8250 UART that uses a 48 MHz
input clock.
Allow these platforms to set up this clock by specifying a kernel command
line like:
earlycon=amdcz,mmio32,0xfedc6000,115200
Signed-off-by: Daniel Kurtz
Suggested-by: Andy Shevchenko
Reviewed-by: Andy Shevchenk
On Wed, Mar 14, 2018 at 7:48 PM Daniel Kurtz wrote:
> Commit 470ca0de69fe ("serial: earlycon: Enable earlycon without command
> line param") added EARLYCON_TABLE().
> Commit 99492c39f39f ("earlycon: Fix __earlycon_table stride") referenced
> commit 07fca0e57fca92 ("tracing: Properly align linker
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
net/ipv4/xfrm4_policy.c
between commit:
d52e5a7e7ca4 ("ipv4: lock mtu in fnhe when received PMTU <
net.ipv4.route.min_pmtu")
from the net tree and commit:
68e813aa4307 ("net/ipv4: Remove fib table id from rtable")
On Tue, Mar 13, 2018 at 8:19 PM, Sinan Kaya wrote:
> Code includes wmb() followed by writel(). writel() already has a barrier
> on some architectures like arm64.
>
> This ends up CPU observing two barriers back to back before executing the
> register write.
>
> Since code already has an explicit b
On Mon, Mar 12, 2018 at 10:29:06PM -0600, Tycho Andersen wrote:
> We're interested in getting rid of all of the stack allocated arrays in the
> kernel [1]. This patch removes one in keys by switching to malloc/free.
> Note that we use kzalloc, to avoid leaking the nonce. I'm not sure this is
> real
On Tue, Mar 13, 2018 at 8:20 PM, Sinan Kaya wrote:
> Code includes wmb() followed by writel(). writel() already has a barrier
> on some architectures like arm64.
>
> This ends up CPU observing two barriers back to back before executing the
> register write.
>
> Since code already has an explicit b
On Tue, Mar 13, 2018 at 8:20 PM, Sinan Kaya wrote:
> Code includes wmb() followed by writel(). writel() already has a barrier
> on some architectures like arm64.
>
> This ends up CPU observing two barriers back to back before executing the
> register write.
>
> Since code already has an explicit b
2018-03-15 0:11 GMT+08:00 Paolo Bonzini :
> On 12/03/2018 12:53, Wanpeng Li wrote:
>> Provides userspace with per-VM capability(KVM_CAP_X86_DISABLE_EXITS) to
>> not intercept MWAIT/HLT/PAUSE in order that to improve latency in some
>> workloads.
>>
>> The patchset implements the original proposal f
Commit 470ca0de69fe ("serial: earlycon: Enable earlycon without command
line param") added EARLYCON_TABLE().
Commit 99492c39f39f ("earlycon: Fix __earlycon_table stride") referenced
commit 07fca0e57fca92 ("tracing: Properly align linker defined symbols")
and tried to fix EARLYCON_TABLE() using __a
On Tue, Mar 13, 2018 at 8:20 PM, Sinan Kaya wrote:
> Code includes wmb() followed by writel() in multiple places. writel()
> already has a barrier on some architectures like arm64.
>
> This ends up CPU observing two barriers back to back before executing the
> register write.
>
> Since code alread
On Tue, Mar 13, 2018 at 8:20 PM, Sinan Kaya wrote:
> Code includes wmb() followed by writel() in multiple places. writel()
> already has a barrier on some architectures like arm64.
>
> This ends up CPU observing two barriers back to back before executing the
> register write.
>
> Since code alread
1 - 100 of 1242 matches
Mail list logo
