All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: xen-devel@lists.xenproject.org
Cc: andr2000@gmail.com, sstabellini@kernel.org,
	Artem_Mygaiev@epam.com, jbeulich@suse.com, Luca.Fancellu@arm.com,
	roger.pau@citrix.com, marmarek@invisiblethingslab.com,
	andrew.cooper3@citrix.com, anthony.perard@vates.tech
Subject: [PATCH 0/2] code style exercise: Drivers folder samples
Date: Sun, 16 Feb 2025 12:21:06 +0200	[thread overview]
Message-ID: <20250216102108.2665222-1-andr2000@gmail.com> (raw)

Hello, everybody!

As agreed before [1] I am sending a series to show two samples of the
formatting done with clang-format. The clang-format configuration can be
found at [2]. It already has some notes on previous discussions when
Luca presented his version of that configuration and which I used to
start from.

There are two diff files which show what happens in case the same is
applied to the whole xen/drivers directory:
- first one is the result of the "git diff" command, 1.2M [3]
- the second one is for "git diff --ignire-all-space", 600K [4]

This is not to limit the reviewers from seeing a bigger picture and not
only the files in this series.
N.B. xen/drivers uses tabs a lot, so this is no surprise the size
difference is big enough: roughly space conversion is half of the changes.

While reviewing the changes I have collected some of the unexpected things
done by clang-format and some interesting pieces. You can find those
below. For some of those I have filed an issue on clang-format and hope the
community will lead me in resolving those. Of course what I collected is
not the complete list of such changes, so I hope we can discuss missed
ones here.

From this exercise I can definitely tell that clang-format does help a
lot and has potential to be employed as a code formatting tool for Xen.
Of course it cannot be used as is now and will require discussions on the
Xen coding style and possibly submitting patches to clang-format to
satisfy those which cannot be handled by the tool now.

Stay safe,
Oleksandr Andrushchenko

1. Const string arrays reformatting
In case the length of items change we might need to introduce a bigger
change wrt new formatting of unaffected lines
==============================================================================

--- a/xen/drivers/acpi/tables.c
+++ b/xen/drivers/acpi/tables.c
@@ -38,10 +38,10 @@
-static const char *__initdata
-mps_inti_flags_polarity[] = { "dfl", "high", "res", "low" };
-static const char *__initdata
-mps_inti_flags_trigger[] = { "dfl", "edge", "res", "level" };
+static const char *__initdata mps_inti_flags_polarity[] = { "dfl", "high",
+                                                            "res", "low" };
+static const char *__initdata mps_inti_flags_trigger[] = { "dfl", "edge", "res",

--- a/xen/drivers/acpi/utilities/utglobal.c
+++ b/xen/drivers/acpi/utilities/utglobal.c
 static const char *const acpi_gbl_region_types[ACPI_NUM_PREDEFINED_REGIONS] = {
-	"SystemMemory",
-	"SystemIO",
-	"PCI_Config",
-	"EmbeddedControl",
-	"SMBus",
-	"CMOS",
-	"PCIBARTarget",
-	"DataTable"
+    "SystemMemory", "SystemIO", "PCI_Config",   "EmbeddedControl",
+    "SMBus",        "CMOS",     "PCIBARTarget", "DataTable"
 };

2. Long strings in ptintk violations
I filed an issue on printk format strings [5]
==============================================================================
@@ -225,9 +231,9 @@ void __init acpi_table_print_madt_entry(struct acpi_subtable_header *header)
         printk(KERN_DEBUG PREFIX
-			       "GIC Distributor (gic_id[0x%04x] address[0x%"PRIx64"] gsi_base[%d])\n",
-			       p->gic_id, p->base_address,
-			       p->global_irq_base);
+               "GIC Distributor (gic_id[0x%04x] address[0x%" PRIx64
+               "] gsi_base[%d])\n",
+               p->gic_id, p->base_address, p->global_irq_base);

@@ -629,12 +628,14 @@ acpi_parse_one_rmrr(struct acpi_dmar_header *header)
-           printk(XENLOG_ERR VTDPREFIX
-                  "Overlapping RMRRs [%"PRIx64",%"PRIx64"] and [%"PRIx64",%"PRIx64"]\n",
-                  rmrru->base_address, rmrru->end_address,
-                  base_addr, end_addr);
+            printk(XENLOG_ERR VTDPREFIX "Overlapping RMRRs [%" PRIx64
+                                        ",%" PRIx64 "] and [%" PRIx64
+                                        ",%" PRIx64 "]\n",
+                   rmrru->base_address, rmrru->end_address, base_addr,
+                   end_addr);

3. String concatenation after clang - needs manual work to fix
==============================================================================
--- a/xen/drivers/acpi/apei/apei-base.c
+++ b/xen/drivers/acpi/apei/apei-base.c
@@ -171,16 +169,19 @@ int __apei_exec_run(struct apei_exec_context *ctx, u8 action,
                 printk(KERN_WARNING
-                               "Invalid action table, unknown instruction "
-                               "type: %d\n", entry->instruction);
+                       "Invalid action table, unknown instruction " "type: %d\n",
+                       entry->instruction);

4. Looks a bit weird, but correct
==============================================================================
--- a/xen/drivers/acpi/apei/apei-io.c
+++ b/xen/drivers/acpi/apei/apei-io.c
@@ -80,13 +78,15 @@ static void __iomem *__init apei_range_map(paddr_t paddr, unsigned long size)
-       pg = ((((paddr + size -1) & PAGE_MASK)
-                - (paddr & PAGE_MASK)) >> PAGE_SHIFT) + 1;
+    pg = ((((paddr + size - 1) & PAGE_MASK) - (paddr & PAGE_MASK)) >>
+          PAGE_SHIFT) +
+         1;

5. Long line tables mess, think it can be manually reformated before applying clang-format
==============================================================================
--- a/xen/drivers/acpi/tables/tbfadt.c
+++ b/xen/drivers/acpi/tables/tbfadt.c
@@ -74,12 +74,12 @@ typedef struct acpi_fadt_info {
-        ACPI_FADT_OFFSET(pm1a_event_block),
-        ACPI_FADT_OFFSET(pm1_event_length), ACPI_FADT_REQUIRED},
+     ACPI_FADT_OFFSET(pm1a_event_block),                                                       ACPI_FADT_OFFSET(pm1_event_length),
+     ACPI_FADT_REQUIRED                                                                                                                                        },

--- a/xen/drivers/acpi/utilities/utglobal.c
+++ b/xen/drivers/acpi/utilities/utglobal.c
@@ -97,71 +96,71 @@ struct acpi_bit_register_info acpi_gbl_bit_register_info[ACPI_NUM_BITREG] = {
     /* Name                                     Parent Register             Register Bit Position                   Register Bit Mask       */
 
     /* ACPI_BITREG_TIMER_STATUS         */ { ACPI_REGISTER_PM1_STATUS,
-						ACPI_BITPOSITION_TIMER_STATUS,
-						ACPI_BITMASK_TIMER_STATUS},
-	/* ACPI_BITREG_BUS_MASTER_STATUS    */ {ACPI_REGISTER_PM1_STATUS,
-						ACPI_BITPOSITION_BUS_MASTER_STATUS,
+                                            ACPI_BITPOSITION_TIMER_STATUS,                                    ACPI_BITMASK_TIMER_STATUS },
+    /* ACPI_BITREG_BUS_MASTER_STATUS    */
+    { ACPI_REGISTER_PM1_STATUS,  ACPI_BITPOSITION_BUS_MASTER_STATUS,

6. Macro blocks are formatted
==============================================================================
Grygorii mentioned this and I was sure it is properly handled, but
it is not. I have filed an issue on clang-format [6].
--- a/xen/drivers/char/cadence-uart.c
+++ b/xen/drivers/char/cadence-uart.c
@@ -189,16 +192,14 @@ static int __init cuart_init(struct dt_device_node *dev, const void *data)
 DT_DEVICE_START(cuart, "Cadence UART", DEVICE_SERIAL)
-    .dt_match = cuart_dt_match,
-    .init = cuart_init,
+    .dt_match = cuart_dt_match, .init = cuart_init,
 DT_DEVICE_END

7. Parentheses for empty functions
==============================================================================
--- a/xen/drivers/char/console.c
+++ b/xen/drivers/char/console.c
@@ -1311,7 +1307,9 @@ void panic(const char *fmt, ...)
-static void cf_check suspend_steal_fn(const char *str, size_t nr) { }
+static void cf_check suspend_steal_fn(const char *str, size_t nr)
+{}

8. Const struct reformatting is weird and inconsistent
==============================================================================
--- a/xen/drivers/char/ns16550.c
+++ b/xen/drivers/char/ns16550.c
@@ -1050,135 +1055,93 @@ static const struct ns16550_config __initconst uart_config[] =
      .param = param_oxford,
      },
     /* Pericom PI7C9X7951 Uno UART */
-    {
-        .vendor_id = PCI_VENDOR_ID_PERICOM,
+    { .vendor_id = PCI_VENDOR_ID_PERICOM,
      .dev_id = 0x7951,
-        .param = param_pericom_1port
-    },
+     .param = param_pericom_1port },

9. Define is longer than 80 chars
==============================================================================
--- a/xen/drivers/cpufreq/cpufreq_ondemand.c
+++ b/xen/drivers/cpufreq/cpufreq_ondemand.c
@@ -27,10 +27,8 @@
-#define MIN_STAT_SAMPLING_RATE                  \
-    (MIN_SAMPLING_MILLISECS * MILLISECS(1))
-#define MIN_SAMPLING_RATE                       \
-    (def_sampling_rate / MIN_SAMPLING_RATE_RATIO)
+#define MIN_STAT_SAMPLING_RATE               (MIN_SAMPLING_MILLISECS * MILLISECS(1))
+#define MIN_SAMPLING_RATE                    (def_sampling_rate / MIN_SAMPLING_RATE_RATIO)

10. Union memebers require an empty line between them
==============================================================================
--- a/xen/drivers/passthrough/amd/iommu-defs.h
+++ b/xen/drivers/passthrough/amd/iommu-defs.h
@@ -289,6 +289,7 @@ struct amd_iommu_dte {
 
 union amd_iommu_control {
     uint64_t raw;
+
     struct {

11. Multiline string alignment for at the first string, not for the function
opening bracket. Depends on the macro before the string?
==============================================================================
--- a/xen/drivers/passthrough/pci.c
+++ b/xen/drivers/passthrough/pci.c
@@ -748,18 +757,18 @@ int pci_add_device(u16 seg, u8 bus, u8 devfn,
             printk(XENLOG_WARNING "SR-IOV device %pp has its virtual"
-                   " functions already enabled (%04x)\n", &pdev->sbdf, ctrl);
+                                  " functions already enabled (%04x)\n",
+                   &pdev->sbdf, ctrl);


11. const struct initializers are inconsistent
I have filed a bug on clang-format for that [7]
==============================================================================

[snip]
static const struct ns16550_config __initconst uart_config[] = {
[snip]
    /* OXPCIe200 1 Native UART  */
    {
     .vendor_id = PCI_VENDOR_ID_OXSEMI,
     .dev_id = 0xc4cf,
     .param = param_oxford,
     },
    /* Pericom PI7C9X7951 Uno UART */
    { .vendor_id = PCI_VENDOR_ID_PERICOM,
     .dev_id = 0x7951,
     .param = param_pericom_1port },
[snip]

[1] https://lists.xen.org/archives/html/xen-devel/2025-02/msg00430.html
[2] https://github.com/andr2000/xen/blob/clang_ml_drivers_v001/xen/.clang-format
[3] https://github.com/andr2000/xen/blob/clang_ml_drivers_v001/xen/drivers.patch
[4] https://github.com/andr2000/xen/blob/clang_ml_drivers_v001/xen/drivers_ignore_all_space.patch
[5] https://github.com/llvm/llvm-project/issues/127383
[6] https://github.com/llvm/llvm-project/issues/127381
[7] https://github.com/llvm/llvm-project/issues/127380

Oleksandr Andrushchenko (2):
  code style: Format ns16550 driver
  code style: Format ACPI tables

 xen/drivers/acpi/tables.c  | 809 ++++++++++++++++++++-----------------
 xen/drivers/char/ns16550.c | 761 +++++++++++++++++-----------------
 2 files changed, 813 insertions(+), 757 deletions(-)

-- 
2.25.1



             reply	other threads:[~2025-02-16 10:21 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-16 10:21 Oleksandr Andrushchenko [this message]
2025-02-16 10:21 ` [PATCH 1/2] code style: Format ns16550 driver Oleksandr Andrushchenko
2025-02-17 10:20   ` Jan Beulich
2025-02-19 12:39     ` Oleksandr Andrushchenko
2025-02-19 13:18       ` Jan Beulich
2025-02-19 13:52         ` Oleksandr Andrushchenko
2025-02-19 14:05           ` Jan Beulich
2025-02-19 15:40             ` Oleksandr Andrushchenko
2025-02-19 16:01               ` Jan Beulich
2025-02-23  7:53                 ` Oleksandr Andrushchenko
2025-02-19 14:23       ` Oleksandr Andrushchenko
2025-02-19 14:58         ` Jan Beulich
2025-02-16 10:21 ` [PATCH 2/2] code style: Format ACPI tables Oleksandr Andrushchenko
2025-02-16 11:58 ` [PATCH 0/2] code style exercise: Drivers folder samples Andrew Cooper
2025-02-16 17:11   ` Oleksandr Andrushchenko
2025-02-19 12:49     ` Andrew Cooper
2025-02-19 12:51       ` Oleksandr Andrushchenko
2025-02-19 13:19         ` Oleksandr Andrushchenko
2025-02-19 13:42           ` Andrew Cooper
2025-02-17  9:07 ` Jan Beulich
2025-02-18  2:36   ` Stefano Stabellini
2025-02-18 11:34     ` Jan Beulich
2025-02-19 12:43       ` Oleksandr Andrushchenko
2025-02-19 12:49         ` Jan Beulich
2025-02-19 12:54           ` Oleksandr Andrushchenko
2025-02-20  1:34             ` Stefano Stabellini
2025-02-23  7:42               ` Oleksandr Andrushchenko
2025-02-24 10:55                 ` Jan Beulich
2025-02-25 18:09                   ` Oleksandr Andrushchenko
2025-02-18  9:56 ` Grygorii Strashko
2025-02-18 11:41   ` Roger Pau Monné
2025-02-19 12:50   ` Oleksandr Andrushchenko
2025-02-18 10:01 ` Luca Fancellu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250216102108.2665222-1-andr2000@gmail.com \
    --to=andr2000@gmail.com \
    --cc=Artem_Mygaiev@epam.com \
    --cc=Luca.Fancellu@arm.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=jbeulich@suse.com \
    --cc=marmarek@invisiblethingslab.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.