On Tue, Jun 15, 2021 at 03:56:46PM +0200, Philippe Mathieu-Daudé wrote:
> On 6/15/21 4:08 AM, David Gibson wrote:
> > On Mon, Jun 14, 2021 at 01:32:11PM -0400, John Snow wrote:
> > In general, what's the convention when a bug is independent of (say)
> > the accel: does it get none of the accel tags
On 6/15/21 9:27 PM, John Snow wrote:
> On 6/14/21 10:08 PM, David Gibson wrote:
>> On Mon, Jun 14, 2021 at 01:32:11PM -0400, John Snow wrote:
>>> Hi, I'd like to work out our collective preferences for how we triage
>>> issues
>>> that concern the execution environment; namely the arch (now
>>> "ta
On 6/14/21 10:08 PM, David Gibson wrote:
On Mon, Jun 14, 2021 at 01:32:11PM -0400, John Snow wrote:
Hi, I'd like to work out our collective preferences for how we triage issues
that concern the execution environment; namely the arch (now "target", os,
and accel labels.
[...]
In general, what
On 6/15/21 10:56 AM, Thomas Huth wrote:
> On 14/06/2021 19.32, John Snow wrote:
> [...]
>> RTH raises the issue of the "TCI" subsystem of TCG, which is not a
>> full accelerator in its own right, but (I think) a special case of
>> TCG. If I keep the 1:1 mapping to ACCEL_CLASS_NAME, "accel: TCI" is
On 6/15/21 4:08 AM, David Gibson wrote:
> On Mon, Jun 14, 2021 at 01:32:11PM -0400, John Snow wrote:
> In general, what's the convention when a bug is independent of (say)
> the accel: does it get none of the accel tags, or all of them?
> Likewise with OS and the other categories.
None: remove the
On 6/15/21 9:28 AM, Cornelia Huck wrote:
> On Mon, Jun 14 2021, John Snow wrote:
>
> (...)
>
>> # OS
>>
>> Currently "os: XXX" for BSD, Linux, Windows, and macOS.
>>
>> https://gitlab.com/qemu-project/qemu/-/labels?subscribed=&search=os%3A
>>
>> Multiple OS labels can be applied to an issue.
>
On 14/06/2021 19.32, John Snow wrote:
[...]
RTH raises the issue of the "TCI" subsystem of TCG, which is not a full
accelerator in its own right, but (I think) a special case of TCG. If I keep
the 1:1 mapping to ACCEL_CLASS_NAME, "accel: TCI" is inappropriate.
Some suggestions:
- "TCI" by itse
On Mon, Jun 14 2021, John Snow wrote:
(...)
> # OS
>
> Currently "os: XXX" for BSD, Linux, Windows, and macOS.
>
> https://gitlab.com/qemu-project/qemu/-/labels?subscribed=&search=os%3A
>
> Multiple OS labels can be applied to an issue.
>
> Originally, we kept this label somewhat vague and have
On Mon, Jun 14, 2021 at 01:32:11PM -0400, John Snow wrote:
> Hi, I'd like to work out our collective preferences for how we triage issues
> that concern the execution environment; namely the arch (now "target", os,
> and accel labels.
>
> If you're CC'd on this mail, you're either listed as a TCG
On 6/14/21 8:53 PM, Philippe Mathieu-Daudé wrote:
> On 6/14/21 7:32 PM, John Snow wrote:
>>
>> # OS
>>
>> Currently "os: XXX" for BSD, Linux, Windows, and macOS.
>>
>> https://gitlab.com/qemu-project/qemu/-/labels?subscribed=&search=os%3A
>>
>> Multiple OS labels can be applied to an issue.
>>
>> O
On 6/14/21 7:32 PM, John Snow wrote:
> # Accel
>
> Currently "accel: XXX", for HAX, HVF, KVM, TCG, WHPX and Xen.
>
> https://gitlab.com/qemu-project/qemu/-/labels?subscribed=&search=accel%3A
>
> Multiple accel labels can be applied to an issue, not just one. The
> intent was to allow for issues
Am 14.06.21 um 19:32 schrieb John Snow:
RTH raises the issue of the "TCI" subsystem of TCG, which is not a
full accelerator in its own right, but (I think) a special case of
TCG. If I keep the 1:1 mapping to ACCEL_CLASS_NAME, "accel: TCI" is
inappropriate.
Some suggestions:
- "TCI" by itself
Hi, I'd like to work out our collective preferences for how we triage
issues that concern the execution environment; namely the arch (now
"target", os, and accel labels.
If you're CC'd on this mail, you're either listed as a TCG maintainer, a
target maintainer, or have been heavily involved in
13 matches
Mail list logo
