Add support of cancellation request to the TEE kernel internal
client interface. Can be used by software TPM drivers, that leverage
TEE under the hood (for instance TPM2.0 mobile profile), for requesting
cancellation of time-consuming operations (RSA key-pair generation etc.).
Signed-off-by: Igor
> On 24 Jan 2019, at 19:15, Vitaly Kuznetsov wrote:
>
> We shouldn't probably be suggesting using Enlightened VMCS when it's not
> enabled (not supported from guest's point of view). System reset through
> synthetic MSR is not recommended neither by genuine Hyper-V nor my QEMU.
>
> Windows
Hi Colin,
sorry dropped of my radar.
On Thu, Jan 24, 2019 at 9:17 AM Alan Tull wrote:
>
> On Thu, Nov 29, 2018 at 5:10 PM Colin King wrote:
>
> Hi Colin,
>
> Thanks!
>
> >
> > From: Colin Ian King
> >
> > Don't populate the const array dummy on the stack but instead
> > make it static. Makes
ping?
On 25/11/2018 17:09, Colin King wrote:
> From: Colin Ian King
>
> Currently, the expression for calculating RON is always going to result
> in zero no matter the value of ram->mr[1] because the ! operator has
> higher precedence than the shift >> operator. I believe the missing
>
On 24/01/2019 17:27, Pierre-Louis Bossart wrote:
>
>> diff --git a/sound/soc/intel/boards/bytcht_es8316.c
>> b/sound/soc/intel/boards/bytcht_es8316.c
>> index fa9c4cf97686..1364e4e601d8 100644
>> --- a/sound/soc/intel/boards/bytcht_es8316.c
>> +++ b/sound/soc/intel/boards/bytcht_es8316.c
>> @@
On 1/24/19 4:34 AM, Rafael J. Wysocki wrote:
> On Tuesday, January 8, 2019 6:00:56 AM CET Viresh Kumar wrote:
>> On 07-01-19, 11:33, Gustavo A. R. Silva wrote:
>>> One of the more common cases of allocation size calculations is finding the
>>> size of a structure that has a zero-sized array at
right, missed that. Thanks!
Addressed this issue + also fixed the description and sent v2.
On Thu, 24 Jan 2019 at 18:19, Jens Wiklander wrote:
>
> On Thu, Jan 24, 2019 at 2:11 PM Igor Opaniuk wrote:
> >
> > Add support of cancellation request to the TEE kernel internal
> > client interface. Can
On 30/11/2018 15:47, Shameer Kolothum wrote:
From: Neil Leeder
Add support for the SMMU Performance Monitor Counter Group
information from ACPI. This is in preparation for its use
in the SMMUv3 PMU driver.
Signed-off-by: Neil Leeder
Signed-off-by: Hanjun Guo
Signed-off-by: Shameer Kolothum
ping?
On 19/12/2018 15:29, Colin King wrote:
> From: Colin Ian King
>
> Currently the uninitialized values in the array reply are printed out
> when exec is false and nvkm_pmu_send has not updated the array. Avoid
> confusion by only dumping out these values if they have been actually
>
diff --git a/sound/soc/intel/boards/bytcht_es8316.c
b/sound/soc/intel/boards/bytcht_es8316.c
index fa9c4cf97686..1364e4e601d8 100644
--- a/sound/soc/intel/boards/bytcht_es8316.c
+++ b/sound/soc/intel/boards/bytcht_es8316.c
@@ -437,7 +437,7 @@ static const struct acpi_gpio_mapping
On Thu, Jan 24, 2019 at 04:51:53PM +, Mark Rutland wrote:
> On Thu, Jan 24, 2019 at 04:19:33PM +, Christophe Leroy wrote:
> > Since only the virtual address of allocated blocks is used,
> > lets use functions returning directly virtual address.
> >
> > Those functions have the advantage
ping?
On 04/09/2018 16:23, Colin King wrote:
> From: Colin Ian King
>
> Don't populate the array vsoff on the stack but instead make it
> static. Makes the object code smaller by 67 bytes:
>
> Before:
>text data bss dec hex filename
>5753 112 0
Hi Dick,
On Fri, Jan 18, 2019 at 03:41:04PM -0600, Dick Hollenbeck wrote:
> Add Cyclone-10 support to altera-ps-spi.c.
> Invert logic involving nCONFIG, nSTATUS, and CONFIG_DONE so it matches
> datasheets
> by going with GPIO_ACTIVE_HIGH instead of GPIO_ACTIVE_LOW in the device
> tree. Add
From: Colin Ian King
Don't populate the const array hw_err on the stack but instead make
it static. Makes the object code smaller by 45 bytes:
Before:
textdata bss dec hex filename
100880 210901088 123058 1e0b2 linux/net/bluetooth/hci_core.o
After:
textdata
On Thu, Jan 24, 2019 at 04:19:43PM +, Christophe Leroy wrote:
> This patch activates CONFIG_THREAD_INFO_IN_TASK which
> moves the thread_info into task_struct.
>
> Moving thread_info into task_struct has the following advantages:
> - It protects thread_info from corruption in the case of
On Thu, Nov 29, 2018 at 5:10 PM Colin King wrote:
Hi Colin,
Thanks!
>
> From: Colin Ian King
>
> Don't populate the const array dummy on the stack but instead
> make it static. Makes the object code smaller by 26 bytes:
>
> Before:
>textdata bss dec hex filename
>7371
We shouldn't probably be suggesting using Enlightened VMCS when it's not
enabled (not supported from guest's point of view). System reset through
synthetic MSR is not recommended neither by genuine Hyper-V nor my QEMU.
Windows seems to be fine either way but let's be consistent.
Fixes:
Hi,
On Thu, Jan 24, 2019 at 10:34:50AM +, nicolas.fe...@microchip.com wrote:
> Hi Sebastian,
>
> On 23/01/2019 at 19:34, Sebastian Reichel wrote:
> > Hi,
> >
> > On Wed, Jan 16, 2019 at 10:57:42AM +0100, Nicolas Ferre wrote:
> >> Add support for additional reset causes and the proper
The pull request you sent on Thu, 24 Jan 2019 16:49:58 +0100:
> https://github.com/ceph/ceph-client.git tags/ceph-for-5.0-rc4
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/22a89a6b88e6db7328292491f564b54b13cc15fb
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Thu, 24 Jan 2019 17:35:27 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git
> fsnotify_for_v5.0-rc4
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/c04e2a780caf7073c31c4289c4b7c3d62f9c0130
Thank you!
--
The pull request you sent on Thu, 24 Jan 2019 10:13:07 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
> tags/sound-5.0-rc4
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/aa7b98459f15bf45d0610c8acfa7929a8641864a
Thank you!
--
Deet-doot-dot,
On 1/23/19 8:48 PM, Nicholas Mc Guire wrote:
Sparse reported warnings about non-static symbols. For the variables
a simple static attribute is fine - for the functions referenced by
livepatch via klp_func the symbol-names must be unmodified in the
symbol table and the patchable code has to be
From: Colin Ian King
Don't populate the const array mic_name on the stack but instead make
it static. Makes the object code smaller by 28 bytes:
Before:
textdata bss dec hex filename
141078832 224 231635a7b bytcht_es8316.o
After:
textdata bss
On Thu 24-01-19 11:00:10, Johannes Weiner wrote:
[...]
> We cannot fully eliminate a risk for regression, but it strikes me as
> highly unlikely, given the extremely young age of cgroup2-based system
> management and surrounding tooling.
I am not really sure what you consider young but this
On Thu, Jan 24, 2019 at 04:19:39PM +, Christophe Leroy wrote:
> [text copied from commit 9bbd4c56b0b6
> ("arm64: prep stack walkers for THREAD_INFO_IN_TASK")]
>
> When CONFIG_THREAD_INFO_IN_TASK is selected, task stacks may be freed
> before a task is destroyed. To account for this, the
Johannes Weiner writes:
I think this increases complexity more than it saves LOC,
unfortunately.
The current situation is a bit repetitive, but much more obviously
correct. And we're not planning on adding many more of those memcg
interface files, so I this doesn't seem to be an improvement re:
ping?
On 26/09/2018 09:41, Colin King wrote:
> From: Colin Ian King
>
> Don't populate the array buf on the stack but instead make it
> static. Makes the object code smaller by 43 bytes:
>
> Before:
>text data bss dec hex filename
>7769 1520 0
There is ample standing to sue. GRSec made it's "access agreement"
public,
which included terms to prevent redistribution (if you redistribute, we
punish you). Which is a direct violation of the "no additional
restrictive terms"
clause in the GPL.
Why won't anyone bring a copyright lawsuit?
On Wed, Jan 23, 2019 at 11:02 PM Asutosh Das wrote:
>
> Adapt to the new ICB framework for bus bandwidth voting.
>
> This requires the source/destination port ids.
> Also this requires a tuple of values.
>
> The tuple is for two different paths - from UFS master
> to BIMC slave. The other is from
On Thu, Jan 24, 2019 at 10:12:10AM -0600, Andrew F. Davis wrote:
> On 1/24/19 9:24 AM, Brian Starkey wrote:
[snip]
> >
> > What do you think about renaming ion_allocation_data.unused to heap_id
> > and adding a flag instead? It's adding cruft to a staging API, but it
> > might soften the
On Thu, Jan 24, 2019 at 04:19:33PM +, Christophe Leroy wrote:
> Since only the virtual address of allocated blocks is used,
> lets use functions returning directly virtual address.
>
> Those functions have the advantage of also zeroing the block.
>
> Suggested-by: Mike Rapoport
> Acked-by:
On Fri, Dec 21, 2018 at 12:51 AM Michal Simek wrote:
>
> On 21. 12. 18 3:37, Manivannan Sadhasivam wrote:
> > On Mon, Oct 29, 2018 at 03:12:44PM +0530, Manivannan Sadhasivam wrote:
> >> For all 96Boards, the following standard is used for onboard LEDs.
> >>
> >> green:user1 default-trigger:
ping?
On 29/11/2018 23:10, Colin King wrote:
> From: Colin Ian King
>
> Don't populate the const array dummy on the stack but instead
> make it static. Makes the object code smaller by 26 bytes:
>
> Before:
>text data bss dec hex filename
>7371 2032
On Thu, Jan 24, 2019 at 10:04:46AM -0600, Andrew F. Davis wrote:
> On 1/23/19 11:11 AM, Brian Starkey wrote:
[snip]
>
> I'm very new to all this, so any pointers to history in this area are
> appreciated.
>
[snip]
>
> > In case you didn't come across it already, the effort which seems to
>
When activating CONFIG_THREAD_INFO_IN_TASK, linux/sched.h
includes asm/current.h. This generates a circular dependency.
To avoid that, asm/processor.h shall not be included in mmu-hash.h
In order to do that, this patch moves into a new header called
asm/task_size_user64.h the information from
One note: If you are going to defend your copyrights and the idea of the
GPL, do not rely on the "free software legal groups".
The "free software legal groups" exist only to commit legal malpractice.
The guy who ran the SFConservancy (Bradly Kuhn IIRC) isn't even a
lawyer. He advises
When moving to CONFIG_THREAD_INFO_IN_TASK, the thread_info 'cpu' field
gets moved into task_struct and only defined when CONFIG_SMP is set.
This patch ensures that TI_CPU is only used when CONFIG_SMP is set and
that task_struct 'cpu' field is not used directly out of SMP code.
Signed-off-by:
Some stack pointers used to also be thread_info pointers
and were called tp. Now that they are only stack pointers,
rename them sp.
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/irq.c | 17 +++--
arch/powerpc/kernel/setup_64.c | 11 +++
2 files changed, 10
40x/booke have another path to reach 3f from transfer_to_handler,
so ACCOUNT_CPU_USER_ENTRY() have to be moved there.
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/entry_32.S | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git
[text copied from commit 9bbd4c56b0b6
("arm64: prep stack walkers for THREAD_INFO_IN_TASK")]
When CONFIG_THREAD_INFO_IN_TASK is selected, task stacks may be freed
before a task is destroyed. To account for this, the stacks are
refcounted, and when manipulating the stack of another task, it is
On Thu, Jan 24, 2019 at 05:15:35PM +0100, Andrew Lunn wrote:
> On Thu, Jan 24, 2019 at 04:07:41PM +, Russell King - ARM Linux admin
> wrote:
> > On Thu, Jan 24, 2019 at 04:51:37PM +0100, Andrew Lunn wrote:
> > > On Thu, Jan 24, 2019 at 02:18:03PM +0100, Thomas Bogendoerfer wrote:
> > > > Set
Since only the virtual address of allocated blocks is used,
lets use functions returning directly virtual address.
Those functions have the advantage of also zeroing the block.
Suggested-by: Mike Rapoport
Acked-by: Mike Rapoport
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/irq.c
On Thu, Jan 24, 2019 at 4:36 PM Javier González wrote:
> It is not pushed anywhere yet, but I have been working on a tool to make
> a pblk recovery tool to enable FTL repairs if something fails in the
> kernel recovery path. Here, I use this uuid to identify the
> instance - is there a way to
On Thu, Jan 24, 2019 at 2:11 PM Igor Opaniuk wrote:
>
> Add support of cancellation request to the TEE kernel internal
> client interface. Can be used by software TPM drivers, that leverage
> TEE under the hood (for instance in TPM2.0 mobile profile), for requesting
> cancellation of
Hi Shijith,
On Thu, Jan 24, 2019 at 07:00:42AM +, Shijith Thotton wrote:
> On 01/23/2019 11:45 PM, Catalin Marinas wrote:
> > diff --git a/arch/arm64/mm/flush.c b/arch/arm64/mm/flush.c
> > index 30695a868107..5c9073bace83 100644
> > --- a/arch/arm64/mm/flush.c
> > +++ b/arch/arm64/mm/flush.c
On Thu, Jan 24, 2019 at 12:01:55PM -0300, Ezequiel Garcia wrote:
> On Tue, 2018-10-30 at 10:15 +0100, Heiko Stuebner wrote:
> > From: Nickey Yang
> >
> > Support Kingdisplay kd097d04 9.7" 1536x2048 TFT LCD panel,
> > it is a MIPI dual-DSI panel.
> >
> > v4-resend:
> > - Thierry noted missing
* Tony Lindgren [190121 17:13]:
> * Felix Brack [190119 17:38]:
> > Hi Tony,
> > On 18.12.18 15:39, Felix Brack wrote:
> > > Remove the unnecessary properties #address-cells and #size-cells
> > > of node pinmux as there are no child-nodes with property reg.
> > >
> > > Signed-off-by: Felix
Clang warns:
drivers/net/ethernet/qlogic/qede/qede_main.c:1183:29: warning: implicit
conversion from enumeration type 'enum qede_rdma_probe_mode' to
different enumeration type 'enum qede_rdma_remove_mode'
[-Wenum-conversion]
qede_rdma_dev_remove(edev, QEDE_RDMA_PROBE_MODE(mode));
On Thu, 24 Jan 2019 16:51:37 +0100
Andrew Lunn wrote:
> On Thu, Jan 24, 2019 at 02:18:03PM +0100, Thomas Bogendoerfer wrote:
> > Set up link interrupt if connection is handled by phylink otherwise
> > link state change detection for in-band-status doesn't work.
>
> Hi Thomas
>
> Please ensure
Hello Linus,
could you please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git
fsnotify_for_v5.0-rc4
to get a fix of fd refcount leak in inotify error path.
Top of the tree is 125892edfe69. The full shortlog is:
Tetsuo Handa (1):
inotify: Fix fd refcount
Hi Tony,
and sorry about the reply latency. This is quite a lot to think about.
I'm also adding Kishon and Mark on CC (e.g. for the phy and ASoC bits).
On Mon, Jan 21, 2019 at 09:01:16AM -0800, Tony Lindgren wrote:
> Hi,
>
> * Johan Hovold [190121 10:57]:
> > Adding Marcel on CC.
> >
> > On
On 2019-01-24 15:31, Enrico Weigelt, metux IT consult wrote:
Do you have some actual proposals / patches ?
Sue Open Source Security / Bradly Spengler for copyright infringement.
Seek his profits as damages. I doubt you'll be able to get specific
performance since the GPL is not a contact in
Hi Alexey, Rob,
On 1/24/19 8:28 AM, Rob Herring wrote:
> On Thu, Jan 24, 2019 at 6:17 AM Alexey Brodkin
> wrote:
>>
>> From: Alexey Brodkin
>>
>> 1. Remove "0x" prefix from unit-address of node names
>> --->8
>> sed -i 's/@0x/@/g'
On Thu, Jan 24, 2019 at 6:17 AM Alexey Brodkin
wrote:
>
> From: Alexey Brodkin
>
> 1. Remove "0x" prefix from unit-address of node names
> --->8
> sed -i 's/@0x/@/g' arch/arc/boot/dts/*.dts*
> --->8
>
> 2.
Introduce hammerhead_defconfig for the LG Nexus 5 phone. Includes
options for USG OTG, WiFi, charger, serial console, gyroscope,
accelerometer, magnetometer, temperature, and pressure sensors.
The necessary options for the display are also included, however the
necessary device tree changes, plus
On Thu, 2019-01-24 at 09:22 -0700, Jens Axboe wrote:
> On 1/24/19 8:09 AM, Jeff Moyer wrote:
> > Jianchao Wang writes:
> >
> > > Swap REQ_NOWAIT and REQ_NOUNMAP and add REQ_HIPRI.
> > >
> > > Signed-off-by: Jianchao Wang
> > > ---
> > > block/blk-mq-debugfs.c | 3 ++-
> > > 1 file changed, 2
On 1/24/19 8:09 AM, Jeff Moyer wrote:
> Jianchao Wang writes:
>
>> Swap REQ_NOWAIT and REQ_NOUNMAP and add REQ_HIPRI.
>>
>> Signed-off-by: Jianchao Wang
>> ---
>> block/blk-mq-debugfs.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/block/blk-mq-debugfs.c
thread_info is not anymore in the stack, so the entire stack
can now be used.
There is also no risk anymore of corrupting task_cpu(p) with a
stack overflow so the patch removes the test.
When doing this, an explicit test for NULL stack pointer is
needed in validate_sp() as it is not anymore
> On 24 Jan 2019, at 17.38, Andy Shevchenko wrote:
>
> On Thu, Jan 24, 2019 at 4:36 PM Javier González wrote:
>
>> It is not pushed anywhere yet, but I have been working on a tool to make
>> a pblk recovery tool to enable FTL repairs if something fails in the
>> kernel recovery path. Here, I
Original Message
Subject: Re: GRSec is vital to Linux security
Date: 2019-01-24 16:25
From: Boris Lukashev
To: linuxgpl...@redchan.it
You've never heard of VMware, I take it? Its a proprietary half Linux
which beats GPL suits with strong arm tactics and technicalities.
On 1/24/19 9:28 AM, Bart Van Assche wrote:
> On Thu, 2019-01-24 at 09:22 -0700, Jens Axboe wrote:
>> On 1/24/19 8:09 AM, Jeff Moyer wrote:
>>> Jianchao Wang writes:
>>>
Swap REQ_NOWAIT and REQ_NOUNMAP and add REQ_HIPRI.
Signed-off-by: Jianchao Wang
---
Please let me know the status of your photos, waiting to retouching them.
Do your photos need white background? sharpen? retouching? We can do it for
you.
Send us the test photos today and we can start to work on them.
Thanks,
Denna
* Heiko Schocher [190121 21:26]:
> Adopt the SPDX license identifier headers to ease license
> compliance management.
Applying into omap-for-v5.1/dt thanks.
Tony
On 1/24/19 3:28 AM, Jianchao Wang wrote:
> Swap REQ_NOWAIT and REQ_NOUNMAP and add REQ_HIPRI.
Applied, thanks.
--
Jens Axboe
This patch cleans the powerpc kernel before activating
CONFIG_THREAD_INFO_IN_TASK:
- The purpose of the pointer given to call_do_softirq() and
call_do_irq() is to point the new stack ==> change it to void* and
rename it 'sp'
- Don't use CURRENT_THREAD_INFO() to locate the stack.
- Fix a few
Now that current_thread_info is located at the beginning of 'current'
task struct, CURRENT_THREAD_INFO macro is not really needed any more.
This patch replaces it by loads of the value at PACACURRENT(r13).
Signed-off-by: Christophe Leroy
---
arch/powerpc/include/asm/exception-64s.h | 4
Now that thread_info is similar to task_struct, its address is in r2
so CURRENT_THREAD_INFO() macro is useless. This patch removes it.
At the same time, as the 'cpu' field is not anymore in thread_info,
this patch renames it to TASK_CPU.
Signed-off-by: Christophe Leroy
---
This patch activates CONFIG_THREAD_INFO_IN_TASK which
moves the thread_info into task_struct.
Moving thread_info into task_struct has the following advantages:
- It protects thread_info from corruption in the case of stack
overflows.
- Its address is harder to determine if stack addresses are
The table of pointers 'current_set' has been used for retrieving
the stack and current. They used to be thread_info pointers as
they were pointing to the stack and current was taken from the
'task' field of the thread_info.
Now, the pointers of 'current_set' table are now both pointers
to
The purpose of this serie is to activate CONFIG_THREAD_INFO_IN_TASK which
moves the thread_info into task_struct.
Moving thread_info into task_struct has the following advantages:
- It protects thread_info from corruption in the case of stack
overflows.
- Its address is harder to determine if
On Thu, 24 Jan 2019 16:07:41 +
Russell King - ARM Linux admin wrote:
> On Thu, Jan 24, 2019 at 04:51:37PM +0100, Andrew Lunn wrote:
> > On Thu, Jan 24, 2019 at 02:18:03PM +0100, Thomas Bogendoerfer wrote:
> > > Set up link interrupt if connection is handled by phylink otherwise
> > > link
On Thu, Jan 24, 2019 at 04:07:41PM +, Russell King - ARM Linux admin wrote:
> On Thu, Jan 24, 2019 at 04:51:37PM +0100, Andrew Lunn wrote:
> > On Thu, Jan 24, 2019 at 02:18:03PM +0100, Thomas Bogendoerfer wrote:
> > > Set up link interrupt if connection is handled by phylink otherwise
> > >
On 24-Jan 16:31, Peter Zijlstra wrote:
> On Thu, Jan 24, 2019 at 12:30:09PM +, Patrick Bellasi wrote:
> > > So I'll have to go over the code again, but I'm wondering why you're
> > > changing uclamp_se::bucket_id on a runnable task.
> >
> > We change only the "requested" value, not the
On 1/24/19 9:24 AM, Brian Starkey wrote:
> Hi Andrew,
>
> On Wed, Jan 23, 2019 at 01:28:35PM -0600, Andrew F. Davis wrote:
>> Previously the heap to allocate from was selected by a mask of allowed
>> heap types. This may have been done as a primitive form of constraint
>> solving, the first heap
On Thu, Jan 24, 2019 at 01:17:18AM -0500, Chris Down wrote:
> memcg has a significant number of files exposed to kernfs where their
> value is either exposed directly or is "max" in the case of
> PAGE_COUNTER_MAX.
>
> There's a fair amount of duplicated code here, since each file involves
>
Good day Sai,
On Wed, 23 Jan 2019 at 13:18, Sai Prakash Ranjan
wrote:
>
> Hi Mathieu,
>
> On 1/24/2019 12:44 AM, Mathieu Poirier wrote:
> > On Wed, 23 Jan 2019 at 05:12, Sai Prakash Ranjan
> > wrote:
> >
> > That depends on whether the ETMs have been modified at all, something
> > Suzuki has
On Thu, Jan 24, 2019 at 04:51:37PM +0100, Andrew Lunn wrote:
> On Thu, Jan 24, 2019 at 02:18:03PM +0100, Thomas Bogendoerfer wrote:
> > Set up link interrupt if connection is handled by phylink otherwise
> > link state change detection for in-band-status doesn't work.
>
> Hi Thomas
>
> Please
On 23/01/2019 21:17, Sai Prakash Ranjan wrote:
> On 1/24/2019 12:44 AM, Mathieu Poirier wrote:
>
>> What version of the Kryo CPU?
>
> There is no Kryo version for MSM8996 (its only given as Kryo), MSM8998
> onwards we have Kryo versions like Kryo 280 and so on. Hence I skipped
> for this one and
On 1/23/19 11:11 AM, Brian Starkey wrote:
> Hi Andrew,
>
> On Wed, Jan 23, 2019 at 10:51:24AM -0600, Andrew F. Davis wrote:
>> On 1/22/19 11:33 AM, Sumit Semwal wrote:
>>> Hello everyone,
>>>
>>> Sincere apologies for chiming in a bit late here, but was off due to
>>> some health issues.
>>>
>>
On 24-Jan 16:15, Peter Zijlstra wrote:
> On Tue, Jan 15, 2019 at 10:15:06AM +, Patrick Bellasi wrote:
> > Add uclamp_default_perf, a special set of clamp values to be used
> > for tasks requiring maximum performance, i.e. by default all the non
> > clamped RT tasks.
>
> Urgh... why though?
On 2019-01-24 12:45 p.m., Ard Biesheuvel wrote:
> On Thu, 24 Jan 2019 at 12:37, Koenig, Christian
> wrote:
>> Am 24.01.19 um 12:26 schrieb Ard Biesheuvel:
>>> On Thu, 24 Jan 2019 at 12:23, Koenig, Christian
>>> wrote:
Am 24.01.19 um 10:59 schrieb Ard Biesheuvel:
> [SNIP]
> This is
On Tue, Jan 22, 2019 at 1:17 AM Leonard Crestez wrote:
>
> On 1/7/2019 9:31 PM, Leonard Crestez wrote:
> > The dts makefiles go through a lot of pointless churn when boards are
> > added. Many SOCs (such as imx) have very simple naming conventions for
> > all boards using a certain chip and board
On Thu, 24 Jan 2019 16:57:11 +0100,
Sameer Pujar wrote:
>
> The runtime PM count is incremented and set to active during hda codec
> device init, but it is decremented and set to suspend during exit only.
> Hence the runtime PM status is always active and hda device cannot be
> put to runtime
On Thu, Jan 24, 2019 at 04:31:10PM +0100, Enrico Weigelt, metux IT consult
wrote:
> On 23.01.19 21:46, Ivan Ivanov wrote:
>
> > Linux really needs to stop adding new features and
> > refactor itself to a smaller and more secure codebase before going
> > forward. Maybe 1 year break would be nice.
On 24-Jan 16:12, Peter Zijlstra wrote:
> On Thu, Jan 24, 2019 at 12:38:35PM +, Patrick Bellasi wrote:
> > On 24-Jan 12:30, Patrick Bellasi wrote:
> > > On 23-Jan 21:11, Peter Zijlstra wrote:
> > > > On Wed, Jan 23, 2019 at 02:40:11PM +, Patrick Bellasi wrote:
> > > > > On 23-Jan 11:49,
On Thu, Jan 24, 2019 at 09:22:52AM +0100, Michal Hocko wrote:
> On Wed 23-01-19 17:31:44, Chris Down wrote:
> > Acked-by: Johannes Weiner
>
> btw. I do not see this patch posted anywhere yet it already comes with
> an ack. Have I just missed a previous version?
I reviewed it offline before
Le 24/01/2019 à 16:01, Christophe Leroy a écrit :
Le 24/01/2019 à 10:43, Christophe Leroy a écrit :
On 01/24/2019 01:06 AM, Michael Ellerman wrote:
Christophe Leroy writes:
Le 12/01/2019 à 10:55, Christophe Leroy a écrit :
The purpose of this serie is to activate
The runtime PM count is incremented and set to active during hda codec
device init, but it is decremented and set to suspend during exit only.
Hence the runtime PM status is always active and hda device cannot be
put to runtime suspend. Keeping device usage active for entire period,
though nothing
In case guest is booted with one CPU present and then later
a sibling CPU is hotplugged [1], it stays offline since SMT
is disabled.
Bisects to
73d5e2b47264 ("cpu/hotplug: detect SMT disabled by BIOS")
which used __max_smt_threads to decide disabling SMT and in
case [1] only primary CPU thread
Currently, tpm_pcr_extend() accepts as an input only a SHA1 digest.
This patch replaces the hash parameter of tpm_pcr_extend() with an array of
tpm_digest structures, so that the caller can provide a digest for each PCR
bank currently allocated in the TPM.
tpm_pcr_extend() will not extend banks
When crypto agility support will be added to the TPM driver, users of the
driver have to retrieve the allocated banks from chip->allocated_banks and
use this information to prepare the array of tpm_digest structures to be
passed to tpm_pcr_extend().
This patch retrieves a tpm_chip pointer from
The tpm_chip structure contains the list of PCR banks currently allocated
in the TPM. When support for crypto agility will be added to the TPM
driver, users of the driver have to provide a digest for each allocated
bank to tpm_pcr_extend(). With this patch, they can obtain the PCR bank
algorithms
Greetings,
I am CAPT. Aston Scholz, United State Army here in Afghanistan, am
seeking your help to evacuate the sum of $7,000,000 to you as long as I
am assured it will be safe That in your care Until I complete my service
here in Afghanistan. This is not stolen money and there are no dangers
Currently, the TPM driver retrieves the digest size from a table mapping
TPM algorithms identifiers to identifiers defined by the crypto subsystem.
If the algorithm is not defined by the latter, the digest size can be
retrieved from the output of the PCR read command.
The patch modifies the
Rename tpm2_* to tpm_* and move the definitions to include/linux/tpm.h so
that these can be used by other kernel subsystems (e.g. IMA).
Signed-off-by: Roberto Sassu
Reviewed-by: Jarkko Sakkinen
Acked-by: Mimi Zohar
---
drivers/char/tpm/tpm-interface.c | 2 +-
drivers/char/tpm/tpm.h
TCG defines two structures, TCG_EfiSpecIDEventStruct and TCG_PCR_EVENT2,
which contain variable-sized arrays in the middle of the definition.
Since these structures are not suitable for type casting, this patch
removes structure members after the variable-sized arrays and adds the
_head suffix to
On 10.01.2019 00:11, Nathan Royce wrote:
Wow, my system got wrecked (exaggeration) during this latest stretch...
Pulseaudio was stretched to the limit and beyond and was forced to
restart. Anything that was producing audio had to be restarted to get
it back.
This time was much like the first
This patch renames active_banks (member of tpm_chip) to allocated_banks,
stores the number of allocated PCR banks in nr_allocated_banks (new member
of tpm_chip), and replaces the static array with a pointer to a dynamically
allocated array.
tpm2_get_pcr_allocation() determines if a PCR bank is
Update
This version of the patch set includes three additional patches (5-7/7)
that allow users of the TPM driver to provide a digest for each PCR bank to
tpm_pcr_extend(). The new patches have been included to facilitate the
review of all the changes to support TPM 2.0 crypto agility for reading
On Thu, Jan 24, 2019 at 02:18:03PM +0100, Thomas Bogendoerfer wrote:
> Set up link interrupt if connection is handled by phylink otherwise
> link state change detection for in-band-status doesn't work.
Hi Thomas
Please ensure the maintainers of the driver are at least on Cc:
Thanks
1001 - 1100 of 1508 matches
Mail list logo
