All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20171016204734.GO1845@lvm>

diff --git a/a/1.txt b/N1/1.txt
index a7bbaf0..1a20ef5 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -29,7 +29,7 @@ non-invasive at runtime for normal VMs.
 > You can create as many VCPUs as you would in a "normal VM". Also, each
 > VCPU can be ran in a kthread.
 > 
-> >  Do you support any form of virtual interrupts? How about timers?
+> >  Do you support any form of virtual interrupts??How about timers?
 > 
 > No support for virtual interrupts or timers indeed. The EFI Runtime
 > Services sandboxing wouldn't require that.
@@ -39,7 +39,7 @@ non-invasive at runtime for normal VMs.
 > The very idea of Runtime Services sandboxing requires Internal VMs to
 > have access to some of the physical devices.
 > 
-> >  How do you debug and trace something like this? Can the VM be
+> >  How do you debug and trace something like this??Can the VM be
 > > monitored from userspace?
 > 
 > There is nothing ready for that.
diff --git a/a/content_digest b/N1/content_digest
index 9811135..e2663f7 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,26 +1,10 @@
  "ref\01503649901-5834-1-git-send-email-florent.revest@arm.com\0"
  "ref\020170831092615.GB13572@cbox\0"
  "ref\01506460492.5507.58.camel@gmail.com\0"
- "From\0Christoffer Dall <cdall@linaro.org>\0"
- "Subject\0Re: [RFC 00/11] KVM, EFI, arm64: EFI Runtime Services Sandboxing\0"
+ "From\0cdall@linaro.org (Christoffer Dall)\0"
+ "Subject\0[RFC 00/11] KVM, EFI, arm64: EFI Runtime Services Sandboxing\0"
  "Date\0Mon, 16 Oct 2017 22:47:34 +0200\0"
- "To\0Florent Revest <revestflo@gmail.com>\0"
- "Cc\0Florent Revest <florent.revest@arm.com>"
-  linux-arm-kernel@lists.infradead.org
-  matt@codeblueprint.co.uk
-  ard.biesheuvel@linaro.org
-  pbonzini@redhat.com
-  rkrcmar@redhat.com
-  christoffer.dall@linaro.org
-  catalin.marinas@arm.com
-  will.deacon@arm.com
-  mark.rutland@arm.com
-  marc.zyngier@arm.com
-  linux-efi@vger.kernel.org
-  linux-kernel@vger.kernel.org
-  kvm@vger.kernel.org
-  kvmarm@lists.cs.columbia.edu
- " leif.lindholm@arm.com\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "On Tue, Sep 26, 2017 at 11:14:52PM +0200, Florent Revest wrote:\n"
@@ -54,7 +38,7 @@
  "> You can create as many VCPUs as you would in a \"normal VM\". Also, each\n"
  "> VCPU can be ran in a kthread.\n"
  "> \n"
- "> >  Do you support any form of virtual interrupts?\302\240How about timers?\n"
+ "> >  Do you support any form of virtual interrupts??How about timers?\n"
  "> \n"
  "> No support for virtual interrupts or timers indeed. The EFI Runtime\n"
  "> Services sandboxing wouldn't require that.\n"
@@ -64,7 +48,7 @@
  "> The very idea of Runtime Services sandboxing requires Internal VMs to\n"
  "> have access to some of the physical devices.\n"
  "> \n"
- "> >  How do you debug and trace something like this?\302\240Can the VM be\n"
+ "> >  How do you debug and trace something like this??Can the VM be\n"
  "> > monitored from userspace?\n"
  "> \n"
  "> There is nothing ready for that.\n"
@@ -88,4 +72,4 @@
  "Thanks,\n"
  -Christoffer
 
-0603d2d07b189771f3d8859ab123d0f1577ed04529cc673ca826340a4d079ab9
+3d047a9825c8c81879cacb495ecc69a5a08786e8e479665eb526b78e7645eb64

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.