On 26/06/24 01:44PM, Cédric Le Goater wrote:
> On 6/23/26 16:19, Aditya Gupta wrote:
> > <...snip...>
> > def do_test_linux_boot(self, command_line =
> > KERNEL_COMMON_COMMAND_LINE):
> > self.require_accelerator("tcg")
> > kernel_path = self.ASSET_KERNEL.fetch()
> > @@ -71,6 +75,88 @@ def test_linux_smt_boot(self):
> > wait_for_console_pattern(self, console_pattern,
> > self.panic_message)
> > wait_for_console_pattern(self, self.good_message,
> > self.panic_message)
> > + def test_linux_remote_interrupts(self):
> > + self.require_accelerator("tcg")
> > + self.set_machine('powernv')
> > +
> > + # have more sockets with as few CPUs as possible, increasing the
> > + # probability to have remote interrupts from one chip to another
> > + # also have e1000e network device to generate interrupts
>
> Can you attach the PCI device to a PCI bus known to be on the
> second socket ? and then offline cpus on the second socket,
> so that all IRQ servers are on the first socket.
Makes sense, thanks cedric ! will keep the device attached to 4th
socket, and offline it's CPU, and let the other setting affinity part
same
Thanks,
- Aditya G
