Hi,
We are pleased to announce the call for presentations for the
Confidential Computing microconference at the Linux Plumbers Conference,
happening in Vienna from September 18th to 20th.
In this microconference we want to discuss ongoing developments around Linux
support for memory encryption an
Hi,
We are pleased to announce that the Confidential Computing Microconference has
been accepted into this years Linux Plumbers Conference, happening from
September 18th to 20th in Vienna, Austria.
With this Call for Registration we want to encourage everyone interested in
this microconference to
On Tue, Jul 17, 2018 at 06:07:07PM +0200, Paul Menzel wrote:
> On a MSI B350M MORTAR with AMD Ryzen 3 2200g (Raven) with Linux 4.18-rc5+
> and Debian Sid/unstable `pci_iommu_init` takes 40 ms according to
> `initcall_debug`.
40ms is a lot indeed, but IOMMU initialization is also a complex process
Hi Paul,
On Tue, Jul 17, 2018 at 06:02:07PM +0200, Paul Menzel wrote:
> $ dmesg
> […]
> [0.145696] calling pci_iommu_init+0x0/0x3f @ 1
> [0.145719] AMD-Vi: Unable to write to IOMMU perf counter.
This is likely a firmware issue. Either the IVRS ACPI table is incorrect
or the BIOS did not
On Sat, Jan 20, 2018 at 05:37:52PM -0800, Joe Perches wrote:
> While Markus' commit messages are nearly universally terrible,
> is there really any signficant value in knowing when any
> particular OOM condition occurs other than the subsystem that
> became OOM?
>
> You're going to be hosed in any
On Sat, Jan 20, 2018 at 03:55:37PM +0100, SF Markus Elfring wrote:
> Do you need any more background information for this general
> transformation pattern?
No.
> Do you find the Linux allocation failure report insufficient for this
> use case?
Yes, because it can't tell me what the code was tryi
On Sat, Jan 20, 2018 at 02:00:13PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sat, 20 Jan 2018 13:51:49 +0100
>
> Omit an extra message for a memory allocation failure in this function.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus E
On Mon, Jan 09, 2017 at 11:41:15PM +0100, Rafael J. Wysocki wrote:
>
> Please find appended.
Applied, thanks.
Hi Rafael,
On Sun, Jan 08, 2017 at 03:20:20AM +0100, Rafael J. Wysocki wrote:
> ---
> drivers/iommu/amd_iommu_init.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Index: linux-pm/drivers/iommu/amd_iommu_init.c
> ===
On Wed, Oct 22, 2014 at 08:00:17PM +0200, SF Markus Elfring wrote:
> drivers/iommu/msm_iommu.c | 3 +--
> drivers/iommu/msm_iommu_dev.c | 6 ++
> 2 files changed, 3 insertions(+), 6 deletions(-)
Applied to arm/msm, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linu
On Fri, Aug 01, 2014 at 06:11:08PM +0200, Borislav Petkov wrote:
> [ 89.040795] pcieport :00:04.0: System wakeup enabled by ACPI
> [ 89.061697] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0
> domain=0x0014 address=0x20001000 flags=0x]
> [ 89.071871] ACPI: Preparing to en
On Tue, Jan 22, 2013 at 09:36:34AM -0500, Boris Ostrovsky wrote:
>
>
> On 01/22/2013 09:13 AM, Udo van den Heuvel wrote:
> >Gigabyte demonstrate that using ESX 5i IOMMU works fine. (with pictures
> >attached).
>
> There are no attachments to your message.
>
> I am not sure that 5i supports IOMM
On Mon, Jan 21, 2013 at 02:09:42PM +0100, Borislav Petkov wrote:
> [0.220022] [Firmware Bug]: AMD-Vi: IOAPIC[9] not in IVRS table
> [0.220078] [Firmware Bug]: AMD-Vi: IOAPIC[10] not in IVRS table
> [0.220132] [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS
> table
> [0.
Hi Boris,
On Mon, Jan 21, 2013 at 09:37:31AM -0500, Boris Ostrovsky wrote:
> Are you talking about erratum 746?
The problems seen here are not about PPR failures, so it is not
particularily this erratum, but the workaround looks similar.
Joerg
--
To unsubscribe from this list: send th
On Sun, Jan 20, 2013 at 12:48:28PM +0100, Borislav Petkov wrote:
> On Sun, Jan 20, 2013 at 12:40:11PM +0100, Jörg Rödel wrote:
> > Yes, the BIOS vendor can fix this issue. They need to disable NB clock
> > gating for the IOMMU.
>
> Right, Udo, you can try Gigabyte first.
>
On Sun, Jan 20, 2013 at 12:25:07PM +0100, Udo van den Heuvel wrote:
> Hello Jörg,
>
> Hardware issue? What is wrong c.q. happening?
I think it falls under Erratum 455 (which does not mention IOMMU
specifically). Point is, there is a hardware workaround for this to make
the IOMMU work, but your BI
On Sun, Jan 20, 2013 at 11:40:20AM +0100, Udo van den Heuvel wrote:
> Hello,
>
> On 2013-01-20 11:36, Borislav Petkov wrote:
> > I know just the guy, CCed. :-)
>
> Thanks for the quick response!
> I found this similar case:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073384
Yes, this
17 matches
Mail list logo
