.snip..
> > Actually as per the boot flow :
> >
> > setup_arch() calls reserve_crashkernel() and pci_iommu_alloc() is
> > invoked through mm_init()/mem_init() and not via initmem_init().
> >
> > start_kernel:
> > ...
> > setup_arch()
> > reserve_crashkernel
> >
On Wed, Jun 24, 2020 at 12:23:57AM +, Ashish Kalra wrote:
> Hello Konrad,
>
> On Tue, Jun 23, 2020 at 09:38:43AM -0400, Konrad Rzeszutek Wilk wrote:
> > On Mon, Apr 27, 2020 at 06:53:18PM +, Ashish Kalra wrote:
> > > Hello Konrad,
> > >
> > > On Mon, Mar 30, 2020 at 10:25:51PM +,
Hello Konrad,
On Tue, Jun 23, 2020 at 09:38:43AM -0400, Konrad Rzeszutek Wilk wrote:
> On Mon, Apr 27, 2020 at 06:53:18PM +, Ashish Kalra wrote:
> > Hello Konrad,
> >
> > On Mon, Mar 30, 2020 at 10:25:51PM +, Ashish Kalra wrote:
> > > Hello Konrad,
> > >
> > > On Tue, Mar 03, 2020 at
On Mon, Apr 27, 2020 at 06:53:18PM +, Ashish Kalra wrote:
> Hello Konrad,
>
> On Mon, Mar 30, 2020 at 10:25:51PM +, Ashish Kalra wrote:
> > Hello Konrad,
> >
> > On Tue, Mar 03, 2020 at 12:03:53PM -0500, Konrad Rzeszutek Wilk wrote:
> > > On Tue, Feb 04, 2020 at 07:35:00PM +, Ashish
Hello Konrad,
On Mon, Mar 30, 2020 at 10:25:51PM +, Ashish Kalra wrote:
> Hello Konrad,
>
> On Tue, Mar 03, 2020 at 12:03:53PM -0500, Konrad Rzeszutek Wilk wrote:
> > On Tue, Feb 04, 2020 at 07:35:00PM +, Ashish Kalra wrote:
> > > Hello Konrad,
> > >
> > > Looking fwd. to your feedback
Hello Konrad,
On Tue, Mar 03, 2020 at 12:03:53PM -0500, Konrad Rzeszutek Wilk wrote:
> On Tue, Feb 04, 2020 at 07:35:00PM +, Ashish Kalra wrote:
> > Hello Konrad,
> >
> > Looking fwd. to your feedback regarding support of other memory
> > encryption architectures such as Power, S390, etc.
>
On Tue, Mar 03, 2020 at 12:03:53PM -0500, Konrad Rzeszutek Wilk wrote:
> > >
> > > >>
> > > >>Actually you seem to be piggybacking on pci_swiotlb_detect_4gb - so
> > > >>perhaps add in this code ? Albeit it really should be in it's own
> > > >>file, not in
On Tue, Feb 04, 2020 at 07:35:00PM +, Ashish Kalra wrote:
> Hello Konrad,
>
> Looking fwd. to your feedback regarding support of other memory
> encryption architectures such as Power, S390, etc.
>
> Thanks,
> Ashish
>
> On Fri, Jan 24, 2020 at 11:00:08PM +, Ashish Kalra wrote:
> > On
Hello Konrad,
Looking fwd. to your feedback regarding support of other memory
encryption architectures such as Power, S390, etc.
Thanks,
Ashish
On Fri, Jan 24, 2020 at 11:00:08PM +, Ashish Kalra wrote:
> On Tue, Jan 21, 2020 at 03:54:03PM -0500, Konrad Rzeszutek Wilk wrote:
> > >
> > >
On Tue, Jan 21, 2020 at 03:54:03PM -0500, Konrad Rzeszutek Wilk wrote:
> >
> > Additional memory calculations based on # of PCI devices and
> > their memory ranges will make it more complicated with so
> > many other permutations and combinations to explore, it is
> > essential to keep this patch
On Thu, Dec 19, 2019 at 08:52:45PM -0500, Konrad Rzeszutek Wilk wrote:
> On Mon, Dec 09, 2019 at 11:13:46PM +, Ashish Kalra wrote:
> > From: Ashish Kalra
> >
> > For SEV, all DMA to and from guest has to use shared
> > (un-encrypted) pages. SEV uses SWIOTLB to make this happen
> > without
On Tue, Jan 21, 2020 at 08:09:47PM +, Ashish Kalra wrote:
> On Thu, Dec 19, 2019 at 08:52:45PM -0500, Konrad Rzeszutek Wilk wrote:
> > On Mon, Dec 09, 2019 at 11:13:46PM +, Ashish Kalra wrote:
> > > From: Ashish Kalra
> > >
> > > For SEV, all DMA to and from guest has to use shared
> > >
On Mon, Dec 09, 2019 at 11:13:46PM +, Ashish Kalra wrote:
> From: Ashish Kalra
>
> For SEV, all DMA to and from guest has to use shared
> (un-encrypted) pages. SEV uses SWIOTLB to make this happen
> without requiring changes to device drivers. However,
> depending on workload being run, the
13 matches
Mail list logo