Removed redundant safety-checks in the code and some debug code that
isn't actually very useful for debugging, like enormous pagetable dump
on each fault. The majority of the changes are code reshuffling,
variables/whitespaces clean up and removal of debug messages that
duplicate messages of the
Fix NULL pointer dereference on IOMMU domain destruction that happens
because clients list is being iterated unsafely and its elements are
getting deleted during the iteration.
Signed-off-by: Dmitry Osipenko
Acked-by: Thierry Reding
---
drivers/iommu/tegra-gart.c | 4 ++--
1 file changed, 2
GART is a part of the Memory Controller driver that is always built-in,
hence there is no benefit from the use of managed resources.
Signed-off-by: Dmitry Osipenko
Acked-by: Thierry Reding
---
drivers/iommu/tegra-gart.c | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
diff
Hello,
This patch-series integrates the GART (IOMMU) driver with the Memory
Controller driver, that allows to report the name of a faulty memory
client on GART page fault. A major code clean up and performance
optimization is performed in this series as well.
Changelog:
v6: v5 that is re-based
Remove unneeded headers inclusion and sort the headers in alphabet order.
Remove pr_fmt macro since there is no pr_*() in the code and it doesn't
affect dev_*() functions.
Signed-off-by: Dmitry Osipenko
Acked-by: Thierry Reding
---
drivers/iommu/tegra-gart.c | 17 +
1 file
Introduce iotlb_sync_map() callback that is invoked in the end of
iommu_map(). This new callback allows IOMMU drivers to avoid syncing
after mapping of each contiguous chunk and sync only when the whole
mapping is completed, optimizing performance of the mapping operation.
Signed-off-by: Dmitry
GART can't handle all devices, hence ignore devices that aren't related
to GART. IOMMU phandle must be explicitly assign to devices in the device
tree.
Signed-off-by: Dmitry Osipenko
Acked-by: Thierry Reding
---
drivers/iommu/tegra-gart.c | 14 +-
1 file changed, 13 insertions(+),
Device tree binding of Memory Controller has been changed: GART has been
squashed into the MC, there are a new mandatory clock and #iommu-cells
properties, the compatible has been changed to 'tegra20-mc-gart'.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra20.dtsi | 15
There could be unlimited number of allocated domains, but only one domain
can be active at a time. Hence devices must be detached only from the
active domain.
Signed-off-by: Dmitry Osipenko
Acked-by: Thierry Reding
---
drivers/iommu/tegra-gart.c | 8 +---
1 file changed, 5 insertions(+), 3
On Mon 2018-12-03 10:45:01, Kalle Valo wrote:
> Pavel Machek writes:
>
> > While grepping something else, I came across LED trigger that is named
> > just "tx".
> >
> > That's a bit too generic afaict?
> >
> > +++ b/drivers/net/wireless/atmel/at76c50x-usb.c
> > @@ -520,7 +520,7 @@ static int
Hi
On Sun, Dec 9, 2018 at 8:39 PM jacopo mondi wrote:
>
> Hi Michael, Jagan, Hans,
>
> On Sat, Dec 08, 2018 at 06:07:04PM +0100, Michael Nazzareno Trimarchi wrote:
> > Hi
> >
> > Down you have my tentative of connection
> >
> > I need to hack a bit to have tuner registered. I'm using imx-media
>
Hi!
(sorry to bring up old thread).
> > > > > Intel(R) SGX is a set of CPU instructions that can be used by
> > > > > applications
> > > > > to set aside private regions of code and data. The code outside the
> > > > > enclave
> > > > > is disallowed to access the memory inside the enclave by
Hi,
On Wed, 5 Dec 2018 11:21:49 +0100
Johan Hovold wrote:
> Fix activation helper which would return -ETIMEDOUT even if the last
> retry attempt was successful.
>
> Also change the semantics of the retries variable so that it actually
> holds the number of retries (rather than tries).
>
From: Steve Longerbeam
Forward events from a sub-device to its list of reachable video
devices.
Note this will queue the event to a video device even if there is
no actual _enabled_ media path from the sub-device to the video device.
So a future improvement is to skip the video device if there
On Fri, Dec 07, 2018 at 06:11:31AM -0800, Paul E. McKenney wrote:
> On Fri, Dec 07, 2018 at 08:25:09AM +, He, Bo wrote:
> > Bad news, the issue is still reproduced after 61 Hours monkey test on 1/6
> > boards with the CONFIG_RCU_BOOST=y, and the issue is not seen on kernel
> > 4.14, the
Add w2sg0004 compatible string since devices without wakeup
pins are now supported.
Signed-off-by: Andreas Kemnade
---
Changes in v2:
- reordering of entries
With the original order there was a
Reviewed-by: Rob Herring
Documentation/devicetree/bindings/gnss/sirfstar.txt | 1 +
1 file
Devices might have a separate lna between antenna output of the gps
chip and the antenna which might have a separate supply.
Signed-off-by: Andreas Kemnade
---
Changes in v2:
- handle lna also if there is no on-off gpio
- rebase on changed 2/5
drivers/gnss/sirf.c | 26
Add lna-supply property.
Signed-off-by: Andreas Kemnade
---
Changes in v2:
- reordering
Original order had a
Reviewed-by: Rob Herring
Documentation/devicetree/bindings/gnss/sirfstar.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/gnss/sirfstar.txt
Some Wi2Wi devices do not have a wakeup output, so device state can
only be indirectly detected by looking whether there is communitcation
over the serial lines.
Additionally it checks for the initial state of the device during
probing to ensure it is off.
Timeout values need to be increased,
The api forbids writing data there otherwise. Prepare for the
serdev_open()/close() being a part of runtime pm.
Signed-off-by: Andreas Kemnade
---
Changes in v2:
add locking
drivers/gnss/sirf.c | 28 +++-
1 file changed, 27 insertions(+), 1 deletion(-)
diff --git
Here is another chapter of the story to get gta04 gnss power
management into the mainline kernel.
There is a w2sg0004 without wakeup line in there, so power state
can only be determined indirectly by looking at the serial data lines.
Then there as also an lna which needs to be powered for real gps
The GPIOAO pins (as well as the two exotic GPIO_BSD_EN and GPIO_TEST_N)
only belong to the pin controller in the AO domain. With the current
definition these pins cannot be referred to in .dts files as group
(which is possible on GXBB and GXL for example).
Add a separate "gpio_aobus" function to
The GPIOAO pins (as well as the two exotic GPIO_BSD_EN and GPIO_TEST_N)
only belong to the pin controller in the AO domain. With the current
definition these pins cannot be referred to in .dts files as group
(which is possible on GXBB and GXL for example).
Add a separate "gpio_aobus" function to
Add the BOOT and CARD pins as GROUP_GROUPs as well so they can be
configured in devicetree using groups = BOOTx or groups = CARDx. This
makes the behavior consistent with other pins inside the same driver as
well as with the BOOT and CARD pins of the GXBB and GXL pinctrl drivers.
Fixes:
Add the BOOT and CARD pins as GROUP_GROUPs as well so they can be
configured in devicetree using groups = BOOTx or groups = CARDx. This
makes the behavior consistent with other pins inside the same driver as
well as with the BOOT and CARD pins of the GXBB and GXL pinctrl drivers.
Fixes:
Rename the existing "gpio" function to "gpio_periphs". This makes it
consistent with the "gpio_aobus" function. Also GXBB and GXL are also
using the "gpio_periphs" naming, so this makes the code here consistent
with other Amlogic pinctrl drivers.
No functional changes since thee "gpio" function
Rename the existing "gpio" function to "gpio_periphs". This makes it
consistent with the "gpio_aobus" function. Also GXBB and GXL are also
using the "gpio_periphs" naming, so this makes the code here consistent
with other Amlogic pinctrl drivers.
No functional changes since thee "gpio" function
While debugging an USB issue on my Odroid-C1 I found a few issues with
the pinctrl driver for the Meson8 and Meson8b SoCs:
- GPIOAO pins cannot be specified as GPIO group in device-tree
- (not a bugfix bug an improvement) make the gpio_periphs group naming
consistent with drivers for newer SoCs
On Sun, Dec 09, 2018 at 10:26:54AM -0800, Dan Williams wrote:
> [ add Willy and Jan ]
>
> On Sun, Dec 9, 2018 at 10:02 AM Linus Torvalds
> wrote:
> >
> > On Sat, Dec 8, 2018 at 10:26 PM Williams, Dan J
> > wrote:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
> > >
On Sun, Dec 09, 2018 at 09:27:01AM -0800, Joe Perches wrote:
> On Sun, 2018-12-09 at 17:20 +0100, Greg KH wrote:
> > On Sun, Dec 09, 2018 at 04:59:00PM +0100, Thomas Jespersen wrote:
> > > This fixes warning reported by sparse (with -Wsparse-all).
> >
> > Why is sparse warning about this?
>
>
Hi Michael, Jagan, Hans,
On Sat, Dec 08, 2018 at 06:07:04PM +0100, Michael Nazzareno Trimarchi wrote:
> Hi
>
> Down you have my tentative of connection
>
> I need to hack a bit to have tuner registered. I'm using imx-media
>
> On Sat, Dec 8, 2018 at 12:48 PM Michael Nazzareno Trimarchi
> wrote:
Hello Rob,
On 12/8/18 12:29 AM, Rob Herring wrote:
> On Mon, Nov 26, 2018 at 11:03:53AM +0100, Parthiban Nallathambi wrote:
>> Actions Semi OWL family SoC's provides support for external interrupt
>> controller to be connected and controlled using SIRQ pins. S500, S700
>> and S900 provides 3 SIRQ
On Wed, 5 Dec 2018 16:09:39 +0100
Johan Hovold wrote:
> On Sun, Nov 18, 2018 at 10:58:01PM +0100, Andreas Kemnade wrote:
> > Add lna-supply property.
> >
> > Signed-off-by: Andreas Kemnade
> > ---
> > Documentation/devicetree/bindings/gnss/sirfstar.txt | 1 +
> > 1 file changed, 1
This is a follow-up to an issue I had a while ago but never had the
time to debug it: [0]
Short summary:
- on Meson8b USB devices are only detected if they are plugged in
before booting Linux
- if they are plugged in after booting Linux they are not detected
(except when running "lsusb -v" as
Disable power_down by setting the parameter to
DWC2_POWER_DOWN_PARAM_NONE. This fixes a problem on various Amlogic
Meson SoCs where USB devices are only recognized when plugged in before
booting Linux. A hot-plugged USB device was not detected even though the
device got power (my USB thumb drive
On Sun 2018-12-09 19:49:42, Jacek Anaszewski wrote:
> Add the flag LED_INIT_DEFAULT_TRIGGER for indicating that trigger
> being set is a default trigger for the LED class device, and
> thus it should be initialized with settings provided in the fwnode.
>
> Set the flag in the
> Set the flag in the led_trigger_set_default(). It is expected to be
> cleared in the activate() op of a trigger after trigger fwnode
> initialization data is parsed and applied. This should happen only
> once after LED class device registration, to allow leaving triggers
> in the idle state on
On Sun 2018-12-09 19:49:41, Jacek Anaszewski wrote:
> It is of no avail to continue iterating through registered
> triggers in the led_trigger_set_default() after the trigger to set
> has been found. Add "break" statement to fix this omission.
>
> Signed-off-by: Jacek Anaszewski
Acked-by: Pavel
On 12/8/18 7:44 PM, Jacek Anaszewski wrote:
Hi Krzysztof,
Thank you for the patch set.
Applied 1/4 and 2/4.
I'll hold on merging 3/4 until we sort out the issues
I have with this one. Please refer to my comment below.
On 12/7/18 1:32 PM, Krzysztof Kozlowski wrote:
Allow initialization of
The pull request you sent on Sun, 9 Dec 2018 06:18:02 +:
> git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
> tags/libnvdimm-fixes-4.20-rc6
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/bd799eb63db4c61a5f2dc941672391fbca5bcab4
Thank you!
--
The pull request you sent on Sun, 9 Dec 2018 12:16:46 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git tags/usb-4.20-rc6
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/50a5528a4b19b7324f0796ea2fedf32530a11ff8
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Sun, 9 Dec 2018 12:18:05 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git
> tags/char-misc-4.20-rc6
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/0844895a2e5161d2fc1674e870a0fd8286a3e18b
Thank you!
--
The pull request you sent on Sat, 8 Dec 2018 13:28:48 -0800:
> git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/6ec067e3a4492569699676d75a21fcee22fefc5b
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Sun, 9 Dec 2018 12:17:17 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tags/tty-4.20-rc6
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/822b7683fff11f152e74c404b3d915f6e5b13698
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Sun, 9 Dec 2018 12:17:37 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
> tags/staging-4.20-rc6
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/47dcb0802d28813e4600192ce27475681f96f230
Thank you!
--
The pull request you sent on Sun, 9 Dec 2018 06:26:39 +:
> git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
> tags/dax-fixes-4.20-rc6
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/fa82dcbf2aed65dc3ea78eaca9ea56fd926b2b10
Thank you!
--
Add the flag LED_INIT_DEFAULT_TRIGGER for indicating that trigger
being set is a default trigger for the LED class device, and
thus it should be initialized with settings provided in the fwnode.
Set the flag in the led_trigger_set_default(). It is expected to be
cleared in the activate() op of a
It is of no avail to continue iterating through registered
triggers in the led_trigger_set_default() after the trigger to set
has been found. Add "break" statement to fix this omission.
Signed-off-by: Jacek Anaszewski
---
drivers/leds/led-triggers.c | 4 +++-
1 file changed, 3 insertions(+), 1
Hi Nayna,
On Sun, 2018-12-09 at 01:56 +0530, Nayna Jain wrote:
> On secure boot enabled systems, a verified kernel may need to kexec
> additional kernels. For example, it may be used as a bootloader needing
> to kexec a target kernel or it may need to kexec a crashdump kernel.
> In such cases, it
Finding endpoints of an IPC channel is one of essential task to
understand how a user program works. Procfs and netlink socket provide
enough hints to find endpoints for IPC channels like pipes, unix
sockets, and pseudo terminals. However, there is no simple way to find
endpoints for an eventfd
On Sun, Dec 9, 2018 at 10:27 AM Dan Williams wrote:
>
> I can send a cleanup, do you want one immediately, or is post -rc6 ok?
post-rc6 is fine, I'd rather have the patch tested anyway,
Linus
Next step: c1bfcad4b0cf38ce5b00f7ad880d3a13484c123a (dma-mapping,
powerpc: simplify the arch dma_set_mask override)
Result: No problems with the PASEMI onboard ethernet and with booting
the X5000 (P5020 board).
-- Christian
On 09 December 2018 at 3:20PM, Christian Zigotzky wrote:
Next
[ add Willy and Jan ]
On Sun, Dec 9, 2018 at 10:02 AM Linus Torvalds
wrote:
>
> On Sat, Dec 8, 2018 at 10:26 PM Williams, Dan J
> wrote:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
> > tags/dax-fixes-4.20-rc6
>
> What's going on with the odd non-exclusive exclusive
The idea here is just to give a demonstration of how one could safely use
the SECCOMP_RET_USER_NOTIF feature to do mount policies. This particular
policy is (as noted in the comment) not very interesting, but it serves to
illustrate how one might apply a policy dodging the various TOCTOU issues.
The const qualifier causes problems for any code that wants to write to the
third argument of the seccomp syscall, as we will do in a future patch in
this series.
The third argument to the seccomp syscall is documented as void *, so
rather than just dropping the const, let's switch everything to
This patch introduces a means for syscalls matched in seccomp to notify
some other task that a particular filter has been triggered.
The motivation for this is primarily for use with containers. For example,
if a container does an init_module(), we obviously don't want to load this
untrusted
Hi all,
Here's v10 of the seccomp trap to userspace series. The only changes
since v9 was to fix up a compilation error in the
!CONFIG_ARCH_HAS_SYSCALL_WRAPPER case, and to add Serge's acks.
Link to v9:
https://lore.kernel.org/lkml/20181203032827.27978-1-ty...@tycho.ws/T/#u
Cheers,
Tycho
In the next patch, we're going to use the sd pointer passed to
__seccomp_filter() as the data to pass to userspace. Except that in some
cases (__seccomp_filter(SECCOMP_RET_TRACE), emulate_vsyscall(), every time
seccomp is inovked on power, etc.) the sd pointer will be NULL in order to
force
On 12/8/18 11:31 PM, Jens Axboe wrote:
> On Dec 8, 2018, at 11:22 PM, Guenter Roeck wrote:
>>
>>> On 12/8/18 9:38 PM, Jens Axboe wrote:
On 12/8/18 5:49 PM, Guenter Roeck wrote:
Hi,
> On Mon, Nov 19, 2018 at 08:18:24AM -0700, Jens Axboe wrote:
> We need a better way of
On Sat, Dec 8, 2018 at 10:26 PM Williams, Dan J
wrote:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
> tags/dax-fixes-4.20-rc6
What's going on with the odd non-exclusive exclusive wait?
prepare_to_wait_exclusive(wq, , TASK_UNINTERRUPTIBLE);
...
/*
From: Vitaly Kuznetsov Sent: Thursday, December 6, 2018
8:58 AM
>
> BIT(13) in HYPERV_CPUID_FEATURES.EBX is described as "ConfigureProfiler" in
> TLFS v4.0 but starting 5.0 it is replaced with 'Reserved'. As we don't
> currently us it in kernel it can just be dropped.
>
> Signed-off-by: Vitaly
On Sun 2018-12-09 08:46:50, Tony Lindgren wrote:
> * Pavel Machek [181209 12:13]:
> > Hi!
> >
> > Poweroff does not seem to work on Motorola droid 4 -- it reboots. It
> > seems to be problem "forever", 4.18 and 4.20-rc5 seem to be
> > affected. It is bad, because when your battery is low, you
From: Vitaly Kuznetsov Sent: Thursday, December 6, 2018
8:58 AM
>
> hyperv-tlfs.h is a bit messy: CPUID feature bits are not always sorted,
> it's hard to get which CPUID they belong to, some items are duplicated
> (e.g. HV_X64_MSR_CRASH_CTL_NOTIFY/HV_CRASH_CTL_CRASH_NOTIFY).
>
> Do some
On 09/12/2018 17:13, Christophe JAILLET wrote:
> Le 09/12/2018 à 16:01, Colin King a écrit :
>> From: Colin Ian King
>>
>> Currently the node == -1 check is being performed twice, the
>> second check is redundant and can be removed. Fix this by
>> removing the redundant second check and moving
(mrph. premature send)
On Sun, 2018-12-09 at 17:20 +0100, Greg KH wrote:
> On Sun, Dec 09, 2018 at 04:59:00PM +0100, Thomas Jespersen wrote:
> > This fixes warning reported by sparse (with -Wsparse-all).
>
> Why is sparse warning about this?
Probably because it's the kernel preferred style
to
On Sun, 2018-12-09 at 17:20 +0100, Greg KH wrote:
> On Sun, Dec 09, 2018 at 04:59:00PM +0100, Thomas Jespersen wrote:
> > This fixes warning reported by sparse (with -Wsparse-all).
>
> Why is sparse warning about this?
Probably because it's the kernel preferred style
to use single statement
On Sun 2018-12-09 08:46:50, Tony Lindgren wrote:
> * Pavel Machek [181209 12:13]:
> > Hi!
> >
> > Poweroff does not seem to work on Motorola droid 4 -- it reboots. It
> > seems to be problem "forever", 4.18 and 4.20-rc5 seem to be
> > affected. It is bad, because when your battery is low, you
Le 09/12/2018 à 16:01, Colin King a écrit :
From: Colin Ian King
Currently the node == -1 check is being performed twice, the
second check is redundant and can be removed. Fix this by
removing the redundant second check and moving the first check
into a combined check with the result from the
Le 09/12/2018 à 16:01, Colin King a écrit :
From: Colin Ian King
Currently the node == -1 check is being performed twice, the
second check is redundant and can be removed. Fix this by
removing the redundant second check and moving the first check
into a combined check with the result from the
Hi!
> On Thu, Nov 15, 2018 at 5:08 PM Jarkko Sakkinen
> wrote:
> >
> > Intel Software Guard eXtensions (SGX) is a set of CPU instructions that
> > can be used by applications to set aside private regions of code and
> > data. The code outside the enclave is disallowed to access the memory
> >
Hi!
> > There would be three types of users:
> >
> > 1. Ones that have access to neither of the devices.
> > 2. Ones that have access to unprivileged. Who are these?
>
> Either 0666 (world) or an sgx group.
Sgx group, please. Or even better, what is generic term for sgx? We
probably want to use
* Pavel Machek [181209 12:13]:
> Hi!
>
> Poweroff does not seem to work on Motorola droid 4 -- it reboots. It
> seems to be problem "forever", 4.18 and 4.20-rc5 seem to be
> affected. It is bad, because when your battery is low, you get into
> reboot loop and discharge it furher, which batteries
On Mon, Oct 29, 2018 at 10:44 PM Kees Cook wrote:
>
> On Mon, Oct 29, 2018 at 7:58 AM, Christian Brauner
> wrote:
> > On Wed, Oct 17, 2018 at 12:33:20AM +0200, Christian Brauner wrote:
> >> Hey,
> >>
> >> Here is v3 of this patchset. Changelogs are in the individual commits.
> >>
> >>
On 07/12/2018 18:59, Palmer Dabbelt wrote:
> On Tue, 04 Dec 2018 02:29:50 PST (-0800), a...@brainfault.org wrote:
>> This patchset extends riscv_timer to provide sched_clock using generic
>> sched_clock framework.
>>
>> The patchset is tested on QEMU virt machine. It is based on
>> Linux-4.20-rc5
Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
Signed-off-by: Yangtao Li
---
drivers/staging/fwserial/fwserial.c | 32 +++
drivers/staging/greybus/loopback.c| 16 ++
drivers/staging/rtlwifi/debug.c | 23 -
On Sun, Dec 09, 2018 at 04:59:00PM +0100, Thomas Jespersen wrote:
> This fixes warning reported by sparse (with -Wsparse-all).
Why is sparse warning about this?
> Signed-off-by: Thomas Jespersen
> ---
> drivers/staging/erofs/internal.h | 4 ++--
> drivers/staging/erofs/utils.c| 4 ++--
> 2
On 12/9/2018 1:20 AM, Andy Shevchenko wrote:
+#ifdef CONFIG_PCI
struct pci_dev *acpi_get_pci_dev(acpi_handle);
+#else
+static inline struct pci_dev *acpi_get_pci_dev(acpi_handle hndl)
Can you spell handle fully?
Yeah, I can do that.
MP2 controllers have two separate busses, so may accommodate up to two I2C
adapters. Those adapters are listed in the ACPI namespace with the
"AMDI0011" HID, and probed by a platform driver.
Communication with the MP2 takes place through iomapped registers, or
through DMA for more than 32 bytes
I intend to give you a portion of my wealth as a free-will financial donation
to you, Respond to partake.
Wang Jianlin
Wanda Group
This fixes warning reported by sparse (with -Wsparse-all).
Signed-off-by: Thomas Jespersen
---
drivers/staging/erofs/internal.h | 4 ++--
drivers/staging/erofs/utils.c| 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/erofs/internal.h
On 12/7/18 12:39 PM, Kristina Martsenko wrote:
> When pointer authentication is in use, data/instruction pointers have a
> number of PAC bits inserted into them. The number and position of these
> bits depends on the configured TCR_ELx.TxSZ and whether tagging is
> enabled. ARMv8.3 allows tagging
On 12/07/2018 02:13 PM, Mason Yang wrote:
> This Renesas R-Car Gen3 RPC SPI driver is based on Boris's new
> spi-mem direct mapping read/write mode [1][2].
>
> v3 patch is according to Marek and Geert's comments including:
> 1) soc_device_mach() to set up RPC_PHYCNT_STRTIM.
> 2) get_unaligned()
From: Colin Ian King
The initialization of ret is redundant as it is being re-assigned to
the return value from the call to imx8m_clk_composite_compute_dividers.
Clean this up by removing the initialization.
Signed-off-by: Colin Ian King
---
drivers/clk/imx/clk-composite-8m.c | 2 +-
1 file
On 12/7/18 12:39 PM, Kristina Martsenko wrote:
> From: Mark Rutland
>
> When pointer authentication is in use, data/instruction pointers have a
> number of PAC bits inserted into them. The number and position of these
> bits depends on the configured TCR_ELx.TxSZ and whether tagging is
>
From: Colin Ian King
Currently the node == -1 check is being performed twice, the
second check is redundant and can be removed. Fix this by
removing the redundant second check and moving the first check
into a combined check with the result from the olpc_ofw call.
Detected by cppcheck:
There are several early memory allocations in arch/ code that use
memblock_phys_alloc() to allocate memory, convert the returned physical
address to the virtual address and then set the allocated memory to zero.
Exactly the same behaviour can be achieved simply by calling
memblock_alloc(): it
There are a several places that allocate memory using memblock APIs that
return a physical address, convert the returned address to the virtual
address and frequently also memset(0) the allocated range.
Update these places to use memblock allocators already returning a virtual
address. Use
The pte_alloc_one_kernel() function allocates a page using
__get_free_page(GFP_KERNEL) when mm initialization is complete and
memblock_phys_alloc() on the earlier stages. The physical address of the
page allocated with memblock_phys_alloc() is converted to the virtual
address and in the both cases
On arm and unicore32i the early_alloc_aligned() and and early_alloc() are
oneliner wrappers for memblock_alloc.
Replace their usage with direct call to memblock_alloc.
Suggested-by: Christoph Hellwig
Signed-off-by: Mike Rapoport
---
arch/arm/mm/mmu.c | 11 +++
Rather than use the memblock_alloc_base that returns a physical address and
then convert this address to the virtual one, use appropriate memblock
function that returns a virtual address.
There is a small functional change in the allocation of then NODE_DATA().
Instead of panicing if the local
Rather than use the memblock_alloc_base that returns a physical address and
then convert this address to the virtual one, use appropriate memblock
function that returns a virtual address.
Signed-off-by: Mike Rapoport
Tested-by: Michal Simek
---
arch/microblaze/mm/init.c | 5 +++--
1 file
Hi,
These patches simplify some of the early memory allocations by replacing
usage of older memblock APIs with newer and shinier ones.
Quite a few places in the arch/ code allocated memory using a memblock API
that returns a physical address of the allocated area, then converted this
physical
On 12/7/18 12:39 PM, Kristina Martsenko wrote:
> From: Mark Rutland
>
> This patch adds basic support for pointer authentication, allowing
> userspace to make use of APIAKey, APIBKey, APDAKey, APDBKey, and
> APGAKey. The kernel maintains key values for each process (shared by all
> threads
On 12/7/18 12:39 PM, Kristina Martsenko wrote:
> From: Mark Rutland
>
> So that we can dynamically handle the presence of pointer authentication
> functionality, wire up probing code in cpufeature.c.
>
> From ARMv8.3 onwards, ID_AA64ISAR1 is no longer entirely RES0, and now
> has four fields
On 12/7/18 12:39 PM, Kristina Martsenko wrote:
> From: Mark Rutland
>
> To allow EL0 (and/or EL1) to use pointer authentication functionality,
> we must ensure that pointer authentication instructions and accesses to
> pointer authentication keys are not trapped to EL2.
>
> This patch ensures
On 12/7/18 12:39 PM, Kristina Martsenko wrote:
> From: Mark Rutland
>
> In subsequent patches we're going to expose ptrauth to the host kernel
> and userspace, but things are a bit trickier for guest kernels. For the
> time being, let's hide ptrauth from KVM guests.
>
> Regardless of how
Hi Omar Sandoval,
On Sat, Dec 1, 2018 at 4:56 AM Omar Sandoval wrote:
>
> On Fri, Nov 30, 2018 at 04:32:40AM -0500, Huijin Park wrote:
> > From: "huijin.park"
> >
> > This patch changes the 'sectors' type to an u64.
> > In 32 bit system, the 'sectors' can accumulate up to about 2TiB.
> > If a
On 12/7/18 12:39 PM, Kristina Martsenko wrote:
> From: Mark Rutland
>
> In KVM we define the configuration of HCR_EL2 for a VHE HOST in
> HCR_HOST_VHE_FLAGS, but we don't have a similar definition for the
> non-VHE host flags, and open-code HCR_RW. Further, in head.S we
> open-code the flags for
On 12/7/18 12:39 PM, Kristina Martsenko wrote:
> To make it clear which exceptions can't be taken to EL1 or EL2, add
> comments next to the ESR_ELx_EC_* macro definitions.
>
> Signed-off-by: Kristina Martsenko
> ---
> arch/arm64/include/asm/esr.h | 14 +++---
> 1 file changed, 7
On Sat, Dec 08, 2018 at 09:47:29PM +0800, Tiwei Bie wrote:
> On Fri, Dec 07, 2018 at 01:10:48PM -0500, Michael S. Tsirkin wrote:
> > On Fri, Dec 07, 2018 at 04:48:42PM +0800, Tiwei Bie wrote:
> > > Switch to using the _SPLIT_ and _PACKED_ variants of vring flags
> > > in split ring and packed ring
601 - 700 of 765 matches
Mail list logo
