In kaslr implementation mechanism, process_e820_entry and
slots_fetch_random are 2 key functions.
process_e820_entry is used to parse passed in memory region and
store available slot area information into array slot_areas[].
slots_fetch_random is used to get a random value and translate
it into st
Kaslr extended kernel text mapping region size from 512M to 1G,
namely CONFIG_RANDOMIZE_BASE_MAX_OFFSET. This means kernel text
can be mapped to below region:
[__START_KERNEL_map + LOAD_PHYSICAL_ADDR, __START_KERNEL_map + 1G]
Introduce a function find_random_virt_offset() to get random value
betw
After register null_blk devices into lightnvm, we forget
to add these devices to the the nullb_list, makes them
invisible to the null_blk driver.
Signed-off-by: Wenwei Tao
---
drivers/block/null_blk.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/block/null_blk.c
On x86_64, in old kaslr implementaion only physical address of kernel
loading is randomized. Then calculate the delta of physical address
where vmlinux was linked to load and where it is finally loaded. If
delta is not equal to 0, namely there's a new physical address where
kernel is actually decom
On Fri, 4 Mar 2016, Shannon Zhao wrote:
> On 2016/3/4 20:24, Stefano Stabellini wrote:
> > On Fri, 4 Mar 2016, Shannon Zhao wrote:
> > > >From: Shannon Zhao
> > > >
> > > >ACPI 6.0 introduces a new table STAO to list the devices which are used
> > > >by Xen and can't be used by Dom0. On Xen virtual
On Fri, Mar 04, 2016 at 07:13:49AM +0100, Krzysztof Hałasa wrote:
> Hi Bjorn,
>
> Bjorn Helgaas writes:
>
> > On Tue, Mar 01, 2016 at 07:07:18AM +0100, Krzysztof Hałasa wrote:
> >> Many ARM platforms use a wrapper:
> >> /*
> >> * Compatibility wrapper for older platforms that do not care about
Function store_slot_info() is used to calculate the slot info of passed
in memory region and store it into slot_areas[].
Function mem_min_overlap is used to iterate all avoid regions to find the
one which overlap with it in the lowest address. E.g there's a memory
region[1024M, 2048M), after itera
Kernel is expected to be randomly reloaded anywhere in the whole
physical memory area, it could be near 64T at most. In this case
there could be about 4*1024*1024 randomization slots if
CONFIG_PHYSICAL_ALIGN is 0x100. Currently the starting address
of candidate position is stored into array slo
Several auxiliary functions and slots[] are not needed any more since
struct slot_area is used to store the slot info of kaslr now. Hence
remove them in this patch.
Signed-off-by: Baoquan He
---
arch/x86/boot/compressed/aslr.c | 24
1 file changed, 24 deletions(-)
diff
From: Yinghai Lu
Now new randomized output can only be chosen from regions above loaded
address. In this case, for bootloaders like kexec which always loads
kernel near the end of ram, it doesn't do randomization at all. Or kernel
is loaded in a very big starting address, we should not give up th
From: Yinghai Lu
We need to include that in boot::decompress_kernel stage to set new
ident mapping.
Also add checking for __pa/__va macro definition, as we need to override them
in boot::decompress_kernel stage.
Reviewed-by: Kees Cook
Signed-off-by: Yinghai Lu
---
arch/x86/include/asm/page.h
On Fri, 4 Mar 2016, Franklin S Cooper Jr. wrote:
> So what you want to happen
> is already happening in the driver. So I don't believe
> simple-bus is needed.
OK great, even better!
- Paul
2016-03-04 18:06 GMT+03:00 Alexander Potapenko :
> On Fri, Mar 4, 2016 at 4:01 PM, Andrey Ryabinin
> wrote:
>> 2016-03-04 17:52 GMT+03:00 Alexander Potapenko :
>>> On Tue, Mar 1, 2016 at 12:57 PM, Andrey Ryabinin
>>> wrote:
>>> +
>>> + stack->hash = hash;
>>> + stack->size =
On 02/03/16 16:24, Arnd Bergmann wrote:
The mediatek XHCI glue driver uses SET_SYSTEM_SLEEP_PM_OPS() to
conditionally set the correct suspend/resume options, and
also puts both the dev_pm_ops and the functions inside of
an #ifdef testing for CONFIG_PM_SLEEP, but those functions
then call other
On Friday 04 March 2016 17:18:23 Paul Bolle wrote:
> [Added Tilman and Christoph.]
>
> On vr, 2016-03-04 at 16:24 +0100, Arnd Bergmann wrote:
> > I actually did more patches that I ended up not submitting:
> >
> > * move hisax to staging
> > * remove i4l support from gigaset
>
> For the record:
On 03/04/2016 09:27 AM, Wenwei Tao wrote:
After register null_blk devices into lightnvm, we forget
to add these devices to the the nullb_list, makes them
invisible to the null_blk driver.
Signed-off-by: Wenwei Tao
---
drivers/block/null_blk.c | 3 ++-
1 file changed, 2 insertions(+), 1 delet
Rename call event names to begin RXRPC_CALL_EV_ to distinguish them from the
flags.
Signed-off-by: David Howells
---
net/rxrpc/ar-accept.c| 10 ++---
net/rxrpc/ar-ack.c | 102 +++---
net/rxrpc/ar-call.c | 14 +++---
net/rxrpc/ar-connev
rxrpc-rewrite
Tagged thusly:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
rxrpc-rewrite-20160304
This is based on net-next/master
David
---
David Howells (13):
rxrpc: Fix a case where a call event bit is being used as a flag bit
rxrpc: Convert call
Convert call flag and event numbers into enums and move their definitions
outside of the struct.
Also move the call state enum outside of the struct and add an extra
element to count the number of states.
Signed-off-by: David Howells
---
net/rxrpc/ar-ack.c |3 +
net/rxrpc/ar-call.c
Fix a case where RXRPC_CALL_RELEASE (an event) is being used to specify a
flag bit. RXRPC_CALL_RELEASED should be used instead.
Signed-off-by: David Howells
---
net/rxrpc/ar-accept.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/rxrpc/ar-accept.c b/net/rxrpc/ar-acc
Forced casts are needed to avoid sparse warning when directly comparing
be32 values.
Signed-off-by: David Howells
---
net/rxrpc/rxkad.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/rxrpc/rxkad.c b/net/rxrpc/rxkad.c
index ca746f382517..3106a0c4960b 100644
--- a/net/
Currently, a copy of the Rx packet header is copied into the the sk_buff
private data so that we can advance the pointer into the buffer,
potentially discarding the original. At the moment, this copy is held in
network byte order, but this means we're doing a lot of unnecessary
translations.
The
Currently, received RxRPC packets outside the range 1-13 are rejected.
There are, however, holes in the range that should also be rejected - plus
at least one type we don't yet support - so reject these also.
Signed-off-by: David Howells
---
include/rxrpc/packet.h | 11 +++
net/rxrpc/
Remove some excess whitespace, insert some missing spaces and adjust a
couple of comments.
Signed-off-by: David Howells
---
net/rxrpc/af_rxrpc.c|9 +++--
net/rxrpc/ar-accept.c |4 +---
net/rxrpc/ar-error.c|1 -
net/rxrpc/ar-internal.h | 22 +++---
net
Clear the unused part of a sockaddr_rxrpc structs so that memcmp() can be
used to compare them.
Signed-off-by: David Howells
---
net/rxrpc/af_rxrpc.c |8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/net/rxrpc/af_rxrpc.c b/net/rxrpc/af_rxrpc.c
index b46f7742d336..a7
Fix the protocol family set in the proto_ops for rxrpc to be PF_RXRPC not
PF_UNIX.
Signed-off-by: David Howells
---
net/rxrpc/af_rxrpc.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/rxrpc/af_rxrpc.c b/net/rxrpc/af_rxrpc.c
index 7bb5cca0ae32..5e810b83269f 100644
---
In the ICMP message processing code, don't try to map ICMP codes to UNIX
error codes as the caller (IPv4/IPv6) already did that for us (ee_errno).
Signed-off-by: David Howells
---
net/rxrpc/ar-error.c | 10 --
1 file changed, 10 deletions(-)
diff --git a/net/rxrpc/ar-error.c b/net/rx
Hi Chris,
On Wed, Mar 02, 2016 at 03:09:35PM -0500, Chris Metcalf wrote:
> Currently ret_fast_syscall, work_pending, and ret_to_user form an ad-hoc
> state machine that can be difficult to reason about due to duplicated
> code and a large number of branch targets.
>
> This patch factors the commo
The upper bound of the defined range for rx_mtu is being set in the same
member as the lower bound (extra1) rather than the correct place (extra2).
I'm not entirely sure why this compiles.
Signed-off-by: David Howells
---
net/rxrpc/sysctl.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(
The version number rxkad places in the response should be network byte
order.
Whilst we're at it, rearrange the code to be more readable.
Signed-off-by: David Howells
---
net/rxrpc/rxkad.c | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/net/rxrpc/rxkad.c
On Thu, Mar 03, 2016 at 08:17:14AM -0800, Greg Kroah-Hartman wrote:
> On Thu, Mar 03, 2016 at 11:37:17AM -0300, Gustavo Padovan wrote:
> > From: Gustavo Padovan
> >
> > Play safe and add flags member to all structs. So we don't need to
> > break API or create new IOCTL in the future if new featur
Use ACCESS_ONCE() when accessing the other-end pointer into a circular
buffer as it's possible the other-end pointer might change whilst we're
doing this, and if we access it twice, we might get some weird things
happening.
Signed-off-by: David Howells
---
net/rxrpc/ar-output.c | 11 +++--
On Wed, Mar 02, 2016 at 01:23:47AM -0500, Hon Ching(Vicky) Lo wrote:
> ibmvtpm_send_crq in tpm_ibmvtpm_suspend returns errors in a more
> granular level than what the existing code does. This patch adds
> the missing CRQ transport event code checks to ensure appropriate
> action taken, in the case
On Fri, Mar 04, 2016 at 04:24:44PM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> Today's linux-next merge of the staging tree got a conflict in:
>
> drivers/media/dvb-frontends/mn88473.c
>
> between commit:
>
> 7908fad99a6c ("[media] mn88473: finalize driver")
>
> from the v4l-dvb tree and
On 03/04/2016 09:29 AM, Kalle Valo wrote:
(Adding Larry)
Geert Uytterhoeven writes:
On Thu, Feb 18, 2016 at 4:28 PM, Kalle Valo wrote:
rtlwifi
* fix broken VHT (802.11ac) support, reported by Linus
That's commit d76d65fd26951498144029c24852c4d54ee512d9
drivers/net/wireless/realtek/rtlw
On 03/04, Maxime Ripard wrote:
> On Thu, Mar 03, 2016 at 11:16:04AM -0800, Stephen Boyd wrote:
> > From: Stephen Boyd
> > Subject: [PATCH] clk: sunxi: Remove use of VLAIS
>
> VLAIS?
Hmm I guess it's just VLA, so llvm won't break. I'll reword
commit text.
>
> > @@ -107,6 +112,8 @@ err_free_div:
The work consisted of:
- Fixed typo in ufshcd-pltfrm.c
- Tweak ufshcd.c for UFS 2.0 support
- Implement ufshcd-dwc which contains all DWC HW specific code
- Unipro attributes were added and new registers were added to the driver
- Implement a tc-dwc-g210 containing G210 MPHY specific code
- Impleme
Adding UFS 2.0 support to the UFS core driver.
Signed-off-by: Joao Pinto
---
Changes v8->v10:
- Nothing changed (just to keep up with patch set version).
Changes v7->v8:
- Added "jedec, ufs-2.0" to the ufschd-platform compatibility strings
Changes v0->v7:
- Nothing changed (just to keep up with p
This patch adds a glue platform driver for the Synopsys G210 Test Chip.
Signed-off-by: Joao Pinto
---
Changes v0->v10:
- This patch only appeared in v10
.../devicetree/bindings/ufs/tc-dwc-g210-pltfrm.txt | 26 +
drivers/scsi/ufs/Kconfig | 9 ++
drivers/scsi/ufs/
This patch adds support for Synopsys G210 Test Chip.
Signed-off-by: Joao Pinto
---
Changes v0->v10:
- This patch only appeared in v10
drivers/scsi/ufs/Kconfig | 4 +
drivers/scsi/ufs/Makefile | 1 +
drivers/scsi/ufs/tc-dwc-g210.c | 315 +
d
Fixed typo in ufshcd-pltfrm.
Signed-off-by: Joao Pinto
---
Changes v0->v10:
- Nothing changed (just to keep up with patch set version).
drivers/scsi/ufs/ufshcd-pltfrm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/ufs/ufshcd-pltfrm.c b/drivers/scsi/ufs/ufshcd
This patch adds a glue pci driver for the Synopsys G210 Test Chip.
Signed-off-by: Joao Pinto
---
Changes v0->v10:
- This patch only appeared in v10
drivers/scsi/ufs/Kconfig | 9 ++
drivers/scsi/ufs/Makefile | 1 +
drivers/scsi/ufs/tc-dwc-g210-pci.c | 178 +
This patch has the goal to add support for DesignWare UFS Controller
specific operations.
Signed-off-by: Joao Pinto
---
Changes v9->v10 (Arnd Bergmann):
- Patch now only has DWC controller specific code
- Added custom_phy_initialization callback for PHY specific code
Changes v8->v9 (Robert Herrin
On Fri, Mar 4, 2016 at 6:08 AM, Radim Krčmář wrote:
> Linux guests on Haswell (and also SandyBridge and Broadwell, at least)
> would crash if you decided to run a host command that uses PEBS, like
> perf record -e 'cpu/mem-stores/pp' -a
>
> This happens because KVM is using VMX MSR switching to
On Fri, 2016-03-04 at 10:44 +0100, Ingo Molnar wrote:
> * Luis R. Rodriguez wrote:
>
> > At kernel summit, during the semantics of ioremap() session, Paul
> > mentioned we'd write something up to help get some notes out on what
> > we need to do and help clarify things. I've run into an issue (ju
Hi Tejun,
I'm doing a summary of this discussion as a part of presenting
Linaro's involvement in Paolo's work. So I try to understand things.
What I'm happy to see is a convergence in the discussion on
timeslicing vs budgeting+time slicing, AFAICT there is consensus
that whatever tool does the jo
On Sun, Feb 28, 2016 at 08:46:16PM -0700, Andrea Righi wrote:
> On Sun, Feb 28, 2016 at 06:53:33PM -0700, Andrea Righi wrote:
> ...
> > I'm using 4.5.0-rc5+, from Linus' git. I'll try to do a git bisect
> > later, I'm pretty sure this problem has been introduced recently (i.e.,
> > I've never seen
On 01/03/16 12:40, Robert Richter wrote:
> On 29.02.16 15:17:53, Laura Abbott wrote:
>> On 02/29/2016 05:30 AM, Marc Zyngier wrote:
>>> On 29/02/16 12:25, Robert Richter wrote:
On 29.02.16 10:46:49, Marc Zyngier wrote:
> On 25/02/16 11:02, Robert Richter wrote:
>> From: Robert Richter
On Fri, Mar 04, 2016 at 09:52:17AM -0500, Sinan Kaya wrote:
[...]
> >> I could integrate the code implementing pci=realloc in patch 11 so
> >> that we realloc by default all resources claimed that failed (which
> >> means that bridges are resized accordingly and you won't be forced
> >> to use pc
On Fri 04-03-16 16:15:58, Michal Hocko wrote:
> On Fri 04-03-16 14:23:27, Joonsoo Kim wrote:
[...]
> > Unconditional 16 looping and then OOM kill really doesn't make any
> > sense, because it doesn't mean that we already do our best.
>
> 16 is not really that important. We can change that if that
On 03/04/2016 04:19 AM, Aleksey Makarov wrote:
> On 03/03/2016 07:40 PM, Peter Hurley wrote:
>> On 03/01/2016 10:19 AM, Aleksey Makarov wrote:
>>> On 03/01/2016 08:22 PM, Peter Hurley wrote:
> On 03/01/2016 05:49 PM, Peter Hurley wrote:
>> On 02/29/2016 04:42 AM, Aleksey Makarov wrote:
On Sat, Mar 05, 2016 at 12:29:39AM +0700, Linus Walleij wrote:
> Hi Tejun,
>
> I'm doing a summary of this discussion as a part of presenting
> Linaro's involvement in Paolo's work. So I try to understand things.
Btw, can someone explain why you guys waste so much time hacking and
arguing about a
On 03/04/2016 03:26 AM, Kirill A. Shutemov wrote:
> On Thu, Mar 03, 2016 at 07:51:50PM +0300, Kirill A. Shutemov wrote:
>> Truncate and punch hole that only cover part of THP range is implemented
>> by zero out this part of THP.
>>
>> This have visible effect on fallocate(FALLOC_FL_PUNCH_HOLE) beha
-and-locking-update/20160304-112229
config: i386-allmodconfig (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
>> ERROR: "i2c_root_adapter" undefined!
>> ERROR: "i2
On 03/03/16 14:34, Shanker Donthineni wrote:
> Hi Marc,
>
> Do you have any comments on this patch?
Not yet. I'll have a look next week.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
On Thu 03-03-16 19:57:44, Hidehiro Kawai wrote:
> Change nmi_panic() macro to a normal function for the portability.
> Also, export it for modules.
I guess you wanted to say
"
Change nmi_panic() from macro to a normal function so that it can be
exported to modules. At least ipmi and hpwdt watchdog
Thanks Marc.
On 03/04/2016 11:46 AM, Marc Zyngier wrote:
> On 03/03/16 14:34, Shanker Donthineni wrote:
>> Hi Marc,
>>
>> Do you have any comments on this patch?
> Not yet. I'll have a look next week.
>
> Thanks,
>
> M.
--
Shanker Donthineni
Qualcomm Technologies, Inc. on behalf of Qualcom
On Mon, Feb 29, 2016 at 03:10:28AM -0800, tip-bot for Thomas Gleixner wrote:
> Commit-ID: b8b3319a471b2df35ae0a8fe94223638468e9ca4
> Gitweb: http://git.kernel.org/tip/b8b3319a471b2df35ae0a8fe94223638468e9ca4
> Author: Thomas Gleixner
> AuthorDate: Mon, 22 Feb 2016 22:19:22 +
> Committ
On Fri, Mar 04, 2016 at 02:23:18PM +0100, Gregory CLEMENT wrote:
> Hi Greg and Jiri,
>
> this is a gentle ping about this patch.
It's in my queue, please be patient given that no one else seems to want
to review this :(
Let's use the of_io_request_and_map() API so that the frame
region is protected and shows up in /proc/iomem.
Cc: Robin Murphy
Signed-off-by: Stephen Boyd
---
This one seems to have been lost in the replies so I'm sending it
seperately.
drivers/clocksource/arm_arch_timer.c | 3 ++-
1 file cha
From: Peter Swain
Some versions can deliver low-level twsi irq before twsi_ctl.iflg
is set, leading to timeout-driven i/o.
When an irq signals event, but woken task does not see the expected
twsi_ctl.iflg, re-check about 80uS later.
EEPROM reads on 100kHz i2c now measure ~5.2kB/s, about 1/2 what
This series for the Octeon i2c driver is an attempt to upstream some
bug fixes and features that accumulated for some time. I tried to
split the cleanup from the other patches and updated the patch
descriptions according to my humble i2c knowledge.
Patches are on top of 4.5-rc6 and were tested o
From: David Daney
Use High Level Controller when possible.
i2c-octeon was reacting badly to bus contention: when in
direct-access mode (for transfers > 8 bytes, which cannot use the
high-level controller) some !ACK or arbitration-loss states were
not causing the current transfer to be aborted, a
Add smbus alert interrupt support.
Signed-off-by: Jan Glauber
---
drivers/i2c/busses/i2c-cavium.h| 6 ++
drivers/i2c/busses/i2c-thunderx-core.c | 35 ++
2 files changed, 41 insertions(+)
diff --git a/drivers/i2c/busses/i2c-cavium.h b/drivers/i2c/buss
The ThunderX SOC uses the same i2c block as the Octeon SOC.
The main difference is that on ThunderX the device is a PCI device
so device probing is done via PCI.
Split the current Octeon driver into an Octeon and a common part
and add the ThunderX support.
Signed-off-by: Jan Glauber
---
drivers
From: David Daney
CN3860 does not interrupt the CPU when the i2c status changes. If
we get a timeout, and see the status has in fact changed, we know we
have this problem, and drop back to polling.
Signed-off-by: David Daney
Signed-off-by: Jan Glauber
---
drivers/i2c/busses/i2c-octeon.c | 46
Cleanup only without functional change.
Signed-off-by: Jan Glauber
Acked-by: David Daney
---
drivers/i2c/busses/i2c-octeon.c | 442 +---
1 file changed, 230 insertions(+), 212 deletions(-)
diff --git a/drivers/i2c/busses/i2c-octeon.c b/drivers/i2c/busses/i2c
From: David Daney
If I2C_M_RECV_LEN is set consider the length byte.
Signed-off-by: David Daney
Signed-off-by: Jan Glauber
---
drivers/i2c/busses/i2c-octeon.c | 15 +--
1 file changed, 13 insertions(+), 2 deletions(-)
diff --git a/drivers/i2c/busses/i2c-octeon.c b/drivers/i2c/bus
From: Peter Swain
Signed-off-by: Peter Swain
Signed-off-by: Jan Glauber
Acked-by: David Daney
---
drivers/i2c/busses/i2c-octeon.c | 19 ---
1 file changed, 12 insertions(+), 7 deletions(-)
diff --git a/drivers/i2c/busses/i2c-octeon.c b/drivers/i2c/busses/i2c-octeon.c
index 0b
From: David Daney
cn78XX has a different interrupt architecture, so we have to manage
the interrupts differently.
Signed-off-by: David Daney
Signed-off-by: Jan Glauber
---
drivers/i2c/busses/i2c-octeon.c | 156 ++--
1 file changed, 136 insertions(+), 20 del
Commit d43de6c780a8 ("akcipher: Move the RSA DER encoding check to
the crypto layer") removed the Kconfig option PUBLIC_KEY_ALGO_RSA,
but forgot to remove a 'select' to this option in the definition of
INTEGRITY_ASYMMETRIC_KEYS.
Let's remove the select, as it's ineffective now.
Signed-off-by: And
Add compatible string for Cavium Octeon cn78XX SOCs TWSI.
Cc: Rob Herring
Cc: Pawel Moll
Cc: Mark Rutland
Cc: Ian Campbell
Cc: Kumar Gala
Signed-off-by: Jan Glauber
Acked-by: David Daney
---
Documentation/devicetree/bindings/i2c/i2c-octeon.txt | 6 ++
1 file changed, 6 insertions(+)
On Thu 04-02-16 15:07:46, Johannes Weiner wrote:
> Rather than scattering mem_cgroup_migrate() calls all over the place,
> have a single call from a safe place where every migration operation
> eventually ends up in - migrate_page_copy().
This is very nice!
> Signed-off-by: Johannes Weiner
> Sug
On Thu 04-02-16 15:07:47, Johannes Weiner wrote:
> Migration accounting in the memory controller used to have to handle
> both oldpage and newpage being on the LRU already; fuse's page cache
> replacement used to pass a recycled newpage that had been uncharged
> but not freed and removed from the L
On Thu, Mar 03, 2016 at 12:29:01PM -0500, Sinan Kaya wrote:
> On 3/3/2016 10:12 AM, Sinan Kaya wrote:
> > On 3/3/2016 10:10 AM, Bjorn Helgaas wrote:
> >> That was my idea, but your minimal patch from last night looks awfully
> >> attractive, and maybe it's not worth moving it to arch/x86. I do thi
On 2016-03-04 12:39, Christoph Hellwig wrote:
On Sat, Mar 05, 2016 at 12:29:39AM +0700, Linus Walleij wrote:
Hi Tejun,
I'm doing a summary of this discussion as a part of presenting
Linaro's involvement in Paolo's work. So I try to understand things.
Btw, can someone explain why you guys wast
Use the more common logging method with the eventual goal
of removing pr_warning altogether.
Miscellanea:
o Realign arguments
o Coalesce formats
o Add missing space between a few coalesced formats
Signed-off-by: Joe Perches
---
kernel/irq/manage.c | 4 ++--
kernel/power/suspe
XSAVES is a kernel-mode instruction. It offers a compacted format and
memory-write optimization. These patches fix known issues in the first
implementation. They are intended for discussion and getting feedback
before actually getting applied.
Version 4 adds a new patch (#9) to fix missing XSAVE l
User space uses standard format xsave area. fpstate in signal frame should
have standard format size.
To explicitly distinguish between xstate size in kernel space and the one
in user space, we rename xstate_size to kernel_xstate_size. This patch is
not fixing a bug. It just makes kernel code more
On Fri, Mar 04, 2016 at 02:01:37PM +0100, Petr Mladek wrote:
>
> Do I understand it correctly that we could not patch functions that
> pass arguments on the stack with this implementation? If yes, how hard
> would be to get it working, please? At least, it would be great to
> catch this problem an
Component offset print out was incorrect for XSAVES. Correct it and move
to a separate function.
Signed-off-by: Yu-cheng Yu
---
arch/x86/kernel/fpu/xstate.c | 18 --
1 file changed, 16 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kernel/fpu/xstate.c b/arch/x86/kernel/fpu/
CPUID function 0x0d, sub function (i, i > 1) returns in ebx the offset of
xstate component i. Zero is returned for a supervisor state. A supervisor
state can only be saved by XSAVES and XSAVES uses a compacted format.
There is no fixed offset for a supervisor state. This patch checks and
makes sure
We did not handle XSAVES* instructions correctly. There were issues in
converting between standard and compacted format when interfacing with
user-space. These issues have been corrected.
Add a WARN_ONCE() to make it clear that XSAVES supervisor states are not
yet implemented.
Signed-off-by: Yu-c
The arrays xstate_offsets[] and xstate_sizes[] record XSAVE area
offsets and sizes. Values for legacy components i387 and XMMs were
not initialized. Fix it.
Signed-off-by: Yu-cheng Yu
---
arch/x86/kernel/fpu/xstate.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/x86/kernel/f
XSAVES uses compacted format and is a kernel instruction. The kernel
should use standard-format, non-supervisor state data for PTRACE.
Signed-off-by: Yu-cheng Yu
---
arch/x86/include/asm/fpu/xstate.h | 4 +
arch/x86/kernel/fpu/regset.c | 56 +---
arch/x86/kernel/fpu/xstate.c
CPUID function 0x0d, sub function (i, i > 1) returns in ecx[1] the
alignment requirement of component i when the compacted format is used.
If ecx[1] is 0, component i is located immediately following the preceding
component. If ecx[1] is 1, component i is located on the next 64-byte
boundary follo
XSAVES is a kernel instruction and uses a compacted format. When
working with user space, the kernel should provide standard-format,
non-supervisor state data. We cannot do __copy_to_user() from a compacted-
format kernel xstate area to a signal frame.
Note that the path to copy_fpstate_to_sigfram
Keep init_fpstate.xsave.header.xfeatures as zero for init optimization.
This is important for init optimization that is implemented in processor.
If a bit corresponding to an xstate in xstate_bv is 0, it means the
xstate is in init status and will not be read from memory to the processor
during XRS
Am 04.03.2016 um 16:24 schrieb Arnd Bergmann:
> On Thursday 03 March 2016 09:30:38 i...@linux-pingi.de wrote:
>> Hi Arnd,
>> I fully agree and ack.
>> Thanks for the work.
>>
>
> I actually did more patches that I ended up not submitting:
>
> * move hisax to staging
> * remove i4l support from gi
This reverts commit 192cb07f7928 ("usb: dwc2: Fix probe problem on
bcm2835") now that we've found the root cause. See the change
titled ("usb: dwc2: Add a 10 ms delay to dwc2_core_reset()").
Signed-off-by: Douglas Anderson
---
drivers/usb/dwc2/core.c | 6 ++
1 file changed, 6 insertions(+)
>From testing and trying to make sense of the documentation, it appears
that a 10 ms delay is needed after resetting the core to make sure that
everything is stable and consistent. Let's add it.
In my testing (on rk3288) this allows us to revert commit
192cb07f7928 ("usb: dwc2: Fix probe problem
ok, no issues and thanks for the information above.I will take care of
these things while sending corrected version of this patch.
Thanks & Regards,
Lokesh
On Fri, Mar 4, 2016 at 5:19 AM, Theodore Ts'o wrote:
> On Thu, Mar 03, 2016 at 10:49:51PM +0530, lokesh jaliminche wrote:
>> Hi,
>>
If "xsaves" is enabled, kernel always uses compacted format of xsave area.
But user space still uses standard format of xsave area. Thus, xstate size
in kernel's xsave area is smaller than xstate size in user's xsave area.
The xstate in signal frame should be in standard format for user's signal
ha
On Thu, Mar 3, 2016 at 8:11 PM, Ken Moffat wrote:
> On Fri, Mar 04, 2016 at 12:44:01AM +, Deucher, Alexander wrote:
>>
>> The attached radeon patch should fix it. I accidently dropped the special
>> handling for NUTMEG DP to VGA bridge chips.
>>
>> > This mobo does not have a DP connector.
>
[Re: runtime regression with "x86/mm/pat: Emulate PAT when it is disabled"] On
03/03/2016 (Thu 22:02) Toshi Kani wrote:
> On Thu, 2016-03-03 at 15:59 -0500, Paul Gortmaker wrote:
> > So, the yocto folks moved from 4.1 to 4.4 and one of their automated
> > qemu x86-32 boot tests started failing.
Signed-off-by: Eric Anholt
---
Documentation/devicetree/bindings/arm/bcm/brcm,bcm2835.txt | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/bcm/brcm,bcm2835.txt
b/Documentation/devicetree/bindings/arm/bcm/brcm,bcm2835.txt
index 11d3056..6ffe087 100644
For now this doesn't support the new hardware present on the Pi 3 (BT,
wifi, GPIO expander). Since the GPIO expander isn't supported, we
also don't have the LEDs like the other board files do.
Signed-off-by: Eric Anholt
---
arch/arm/boot/dts/Makefile| 3 +-
arch/arm/boot/dts/bcm283
Hi Clemens,
On March 4, 2016 8:07:40 AM GMT+00:00, Clemens Ladisch
wrote:
>Felipe Ferreri Tonello wrote:
>> On 03/03/16 11:38, Clemens Ladisch wrote:
>>> But in what way was the old state machine not "proper"?
>>
>> Because it didn't reflect all the correct and possible MIDI states
>
>The whole
On Fri, Mar 04, 2016 at 10:39:29AM -0800, Eric Anholt wrote:
> For now this doesn't support the new hardware present on the Pi 3 (BT,
> wifi, GPIO expander). Since the GPIO expander isn't supported, we
> also don't have the LEDs like the other board files do.
>
> Signed-off-by: Eric Anholt
> ---
Hi Balbi,
On March 4, 2016 7:13:05 AM GMT+00:00, Felipe Balbi wrote:
>"Felipe F. Tonello" writes:
>> [ text/plain ]
>> Signed-off-by: Felipe F. Tonello
>
>no commit log == no commit
Got it.
>
>> ---
>> drivers/usb/gadget/function/f_midi.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> d
501 - 600 of 912 matches
Mail list logo
